We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have some automation that cancels ongoing Jenkins runs for PRs when a new commit is pushed. For example, https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/20052/ was aborted when https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/20053/ started.
When this happens the cancelled job says:
11:00:49 Build was aborted 11:00:49 Aborted by unknown 11:00:49 Recording test results
It would be nice if the job canceller identified itself, rather than showing up as unknown.
Imported from Jira BEAM-13469. Original Jira may contain additional context. Reported by: bhulette.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We have some automation that cancels ongoing Jenkins runs for PRs when a new commit is pushed. For example, https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/20052/ was aborted when
https://ci-beam.apache.org/job/beam_PreCommit_Java_Commit/20053/ started.
When this happens the cancelled job says:
It would be nice if the job canceller identified itself, rather than showing up as unknown.
Imported from Jira BEAM-13469. Original Jira may contain additional context.
Reported by: bhulette.
The text was updated successfully, but these errors were encountered: