What happened:
Changes made in the PR #3252 relied on the status of the builds that were created during event creation to identify virtual builds.
There could be scenarios when the non-virtual job builds may not be queued for execution and remain in CREATED status. This may lead to incorrectly identifying them as virtual builds (status would be updated to SUCCESS and downstream jobs would be triggered)
What you expected to happen:
Switch to more reliable approach to identify virtual job builds.
How to reproduce it:
What happened:
Changes made in the PR #3252 relied on the
statusof the builds that were created during event creation to identify virtual builds.There could be scenarios when the non-virtual job builds may not be queued for execution and remain in
CREATEDstatus. This may lead to incorrectly identifying them as virtual builds (status would be updated toSUCCESSand downstream jobs would be triggered)What you expected to happen:
Switch to more reliable approach to identify virtual job builds.
How to reproduce it: