Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI (Buildkite, GHA): Allow any user with triage or commit permissions to retry all failed Buildkite jobs #42138

Merged
merged 6 commits into from
Sep 11, 2021

Conversation

DilumAluthge
Copy link
Member

@DilumAluthge DilumAluthge commented Sep 7, 2021

This PR adds a GitHub Actions workflow that allows any user with triage or commit permissions to retry all failed Buildkite jobs by adding the Buildkite - retry failed jobs label.

The key points are:

  1. Any user with triage or commit permissions can do this.
  2. Users do not need to create a Buildkite account. They just add the Buildkite - retry failed jobs label to the PR.
  3. It only reruns failed Buildkite jobs. It doesn't rerun any passed Buildkite jobs, which helps conserve CI resources.

TODO before merging:

  • Remove the trailing whitespace
  • Change pull_request to pull_request_target

@DilumAluthge DilumAluthge added ci Continuous integration backport 1.6 Change should be backported to release-1.6 backport 1.7 and removed Buildkite - retry failed jobs labels Sep 7, 2021
@DilumAluthge DilumAluthge force-pushed the dpa/retry-failed-buildkite-jobs branch from e92e691 to 322b23a Compare September 7, 2021 04:11
@DilumAluthge DilumAluthge changed the title Allow any user with triage or commit permissions to retry all failed Buildkite jobs CI (Buildkite): Allow any user with triage or commit permissions to retry all failed Buildkite jobs Sep 7, 2021
DilumAluthge added a commit to JuliaLang/buildkite-rerun-failed that referenced this pull request Sep 11, 2021
DilumAluthge added a commit to JuliaLang/buildkite-rerun-failed that referenced this pull request Sep 11, 2021
@DilumAluthge
Copy link
Member Author

@staticfloat I've moved all of the Julia code to a composite action (https://github.com/JuliaLang/retry-buildkite), that we then use in the YAML workflow file in this repository.

@DilumAluthge
Copy link
Member Author

Also, by putting this functionality into a composite action, we can use it on other repos.

It will work on any repo that uses Buildkite. Just add a Buildkite API token as a GitHub Secret on the repo.

@DilumAluthge DilumAluthge added merge me PR is reviewed. Merge when all tests are passing and removed Buildkite - retry failed jobs labels Sep 11, 2021
@DilumAluthge
Copy link
Member Author

The two TODOs are done.

@DilumAluthge DilumAluthge merged commit 5047920 into master Sep 11, 2021
@DilumAluthge DilumAluthge deleted the dpa/retry-failed-buildkite-jobs branch September 11, 2021 05:11
@DilumAluthge DilumAluthge removed the merge me PR is reviewed. Merge when all tests are passing label Sep 11, 2021
KristofferC pushed a commit that referenced this pull request Sep 11, 2021
… to retry all failed Buildkite jobs (#42138)

(cherry picked from commit 5047920)
KristofferC pushed a commit that referenced this pull request Sep 15, 2021
… to retry all failed Buildkite jobs (#42138)

(cherry picked from commit 5047920)
KristofferC pushed a commit that referenced this pull request Nov 11, 2021
… to retry all failed Buildkite jobs (#42138)

(cherry picked from commit 5047920)
@KristofferC KristofferC removed the backport 1.6 Change should be backported to release-1.6 label Nov 13, 2021
LilithHafner pushed a commit to LilithHafner/julia that referenced this pull request Feb 22, 2022
LilithHafner pushed a commit to LilithHafner/julia that referenced this pull request Mar 8, 2022
staticfloat pushed a commit that referenced this pull request Dec 23, 2022
… to retry all failed Buildkite jobs (#42138)

(cherry picked from commit 5047920)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Continuous integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants