Don't rerun CI jobs on every label change #6230
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes the
ci-build-me
bot check for running or finished buildkite jobs before attempting to start a new one. Currently, changing a label (e.g. addingready-to-merge-into-develop
) will re-run CI even if the CI job has already been executed and has finished.This change only affects the behaviour of the
ci-build-me
label; commenting with!ci-build-me
will still always trigger a new build, and may be used to trigger re-runs if flaky tests are causing a failure.Checklist: