# Open the \`cancel\` button permission to allow contributors to terminate the \`matrix\` build job

**URL:** <https://travis-ci.community/t/open-the-cancel-button-permission-to-allow-contributors-to-terminate-the-matrix-build-job/101>\
**Category:** Travis CI Discussions & Feedback\
**Tags:** web-ui\
**Created:** [August 5, 2018, 11:02pm UTC](https://travis-ci.community/t/open-the-cancel-button-permission-to-allow-contributors-to-terminate-the-matrix-build-job/101 "2018-08-05T23:02:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![asdf2014](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/asdf2014/32/55_2.png) [@asdf2014](https://travis-ci.community/u/asdf2014)\
**Post date:** [August 5, 2018, 11:02pm UTC](https://travis-ci.community/t/open-the-cancel-button-permission-to-allow-contributors-to-terminate-the-matrix-build-job/101/1 "2018-08-05T23:02:37Z")

</div>

Is there any plan to open the `cancel` button permission to allow contributors to terminate the `matrix` build job? Not only is it harmless, it also saves travis resources.

---

<div class="post-metadata">

**Author:** ![acnagy](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/acnagy/32/17_2.png) [@acnagy](https://travis-ci.community/u/acnagy)\
**Post date:** [August 7, 2018, 11:12pm UTC](https://travis-ci.community/t/open-the-cancel-button-permission-to-allow-contributors-to-terminate-the-matrix-build-job/101/2 "2018-08-07T23:12:11Z")

</div>

Hi, hi @asdf2014! Right now, this is not on the roadmap, but it’s got an internally tracked issue… I linked your comment ([here](https://github.com/travis-pro/post-its/issues/118) for Travis CI folks) and will let you know if/when it’s added.

In the meantime, I just wanted to say, I do really like the idea, though I’ll have to scope out the complexity of that change - we get the permissions for who can cancel builds based on who has write/push access to a repo, and it should be a simple things to split this out – question is (a) am I right? and (b) verifying the UX works in other cases as well.

---

<div class="post-metadata">

**Author:** ![asdf2014](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/asdf2014/32/55_2.png) [@asdf2014](https://travis-ci.community/u/asdf2014)\
**Post date:** [August 8, 2018, 9:48am UTC](https://travis-ci.community/t/open-the-cancel-button-permission-to-allow-contributors-to-terminate-the-matrix-build-job/101/3 "2018-08-08T09:48:18Z")

</div>

Hi, @acnagy . Wonderful, looking forward to.

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [November 13, 2018, 1:50pm UTC](https://travis-ci.community/t/open-the-cancel-button-permission-to-allow-contributors-to-terminate-the-matrix-build-job/101/4 "2018-11-13T13:50:09Z")

</div>

Previous comments are found in [https://github.com/travis-ci/travis-ci/issues/887](https://github.com/travis-ci/travis-ci/issues/887)

---

<div class="post-metadata">

**Author:** ![cognifloyd](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/cognifloyd/32/471_2.png) [@cognifloyd](https://travis-ci.community/u/cognifloyd)\
**Post date:** [November 15, 2018, 5:51am UTC](https://travis-ci.community/t/open-the-cancel-button-permission-to-allow-contributors-to-terminate-the-matrix-build-job/101/5 "2018-11-15T05:51:58Z")

</div>

> [@acnagy](#):
>
> based on who has write/push access to a repo

It needs to be more than just people with write/push access to a repo.  
If I submit a PR, I should be able to cancel the builds _for my PR_, even though I don’t have access to the destination repo. I know when I have made a mistake or I’m about to submit a follow up commit to the PR. Please let me cancel builds that are no longer needed for my PRs.

In other words, it would be people who have write/push access to the source branch/repo that the PR is coming from, not just the oeople with write/push access to the repo that is receiving the PR (and that triggered the Travis build).
