jjb: Immediately remove currentJobs with null build
authorKienan Stewart <kstewart@efficios.com>
Tue, 20 Jun 2023 15:30:08 +0000 (11:30 -0400)
committerKienan Stewart <kstewart@efficios.com>
Tue, 20 Jun 2023 15:30:08 +0000 (11:30 -0400)
commiteedda9798a7ef2d43fda1ebf5fd238f2b52532b1
treec3b2b1734c80c3b40bafec095b528a76e24080ad
parent7033367ae2fd2ea02f3920cef09f794b4986ff2b
jjb: Immediately remove currentJobs with null build

In 9ee19c2b8f8af895460c3cc132282a9f85ec27dd, jobs ended up getting set
as 'Cancelled' if LaunchJob returned null instead of a Job
object. Those cancellations meant that the entire result of the
trigger was set to 'Aborted', masking otherwise successful runs.

This commit changes the behaviour slightly by prunning entries with a
null build immediately after the jobs are queued. This means that jobs
that couldn't be found by name don't cause the build to be flagged as
'Aborted'.

Change-Id: Ie76bb7bf05625eb541b0abdf0f05e95eb2d740c4
scripts/system-tests/system-trigger.groovy
This page took 0.022807 seconds and 4 git commands to generate.