Investigate broadening CircleCI build access

[eloquence]

Originally filed in our infrastructure repository on 2017-10-16, migrating here for visibility/discussion.

SecureDrop maintainers should have the ability to restart/kill CI builds. Currently they do not.

User Story

As a maintainer, I want to be able restart or kill builds in case of problems, so I'm not bottlenecked on others doing so.

[eloquence]

We touched base at the engineering meeting on 4/19 about this. @msheiny will investigate what our options are. @harrislapiroff reported that he is able to restart builds on another repo without being the owner.

[msheiny]

After some investigation with faux accounts, this seems to be accessible (as @harrislapiroff noted) but any user with write access to the repository. @dachary / @kushaldas - in order to do this you have to sign into circleci when you go to the build page using the OAuth Github link. You should then be able to drill into the workflow and re-run jobs.

Here is an example of where to find that... (Note the link below that says Workflow: securedrop_ci

If you follow the workflow , you'll get to the following page where you can either rerun everything or rerun failed jobs. Whenever @kushaldas or @dachary ping me for re-running i typically run that task so it only runs the tasks that failed again.

[ghost]

I confirm I have access. Awesome !

[eloquence]

Excellent. Let's wait for @heartsucker or @kushaldas to confirm and then we can close this.

[heartsucker]

Confirmed access :D

[eloquence]

Hooray! Closing this issue. @kushaldas please speak up if this explanation doesn't work for you. :)