Flaky CI builds

[jglick]

From #192, #208, and master.

[basil]

PRs like this that consume an unmerged and/or unreleased upstream change need to remain in draft state until the upstream change is merged and released.

[jglick]

Referring to jenkinsci/plugin-compat-tester#228? Yes in general. At least as of jenkinsci/plugin-compat-tester#255 the unreleased upstream change is easier to identify.

For now we are still stuck on jenkinsci/plugin-compat-tester#345 since none of us has had time to work on a proper supportable patch or even make the current patches be activated by some sort of experimental flag. #657

[basil]

#657 could have been avoided had we refrained from consuming an unmerged and/or unreleased upstream change in a non-draft PR.

[jglick]

Yes, it could; we prioritized getting bom builds working reliably and handling ongoing plugin releases.