[
https://issues.apache.org/jira/browse/BEAM-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17549704#comment-17549704
]
Danny McCormick commented on BEAM-13469:
----------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/21277
> Jenkins job canceller should identify itself
> --------------------------------------------
>
> Key: BEAM-13469
> URL: https://issues.apache.org/jira/browse/BEAM-13469
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Brian Hulette
> Priority: P3
>
> 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:
> {code}
> 11:00:49 Build was aborted
> 11:00:49 Aborted by unknown
> 11:00:49 Recording test results
> {code}
> It would be nice if the job canceller identified itself, rather than showing
> up as unknown.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
