Test `weekly` BOM more frequently

[jglick]

#746 (comment)

[basil]

Seems to me that the BOM tests should be run on every core PR before it is accepted—if not on every revision (due to cost), then at least once the PR is labelled with ready-for-merge, in order to ensure there are no regressions.

[jglick]

If you can figure out how to set that up, it would be great. Or something like jenkinsci/maven-hpi-plugin#66. Or use Launchable to run some tests which seem important (not that that would likely have caught the need for jenkinsci/jenkins#6040).

[basil]

Brainstorming out loud: what if additional GitHub metadata, such as the set of labels or a boolean indicating whether auto-merge is enabled, were exposed to Pipeline jobs? Then the Jenkinsfile could be amended to run additional tests when the change is ready to land or in the process of landing.

[jglick]

I think there is a plugin that lets you do that. It cannot however trigger a build when labels change.

[jglick]

In a similar vein, CloudBees CI PCT runs roughly corresponding to jenkinsci/jenkins@master caught prior to today’s weekly release: jenkinsci/forensics-api-plugin#572

(Tried to confirm with local-test.sh but was unable to build bom today due to org.eclipse.mylyn.github:org.eclipse.egit.github.core:jar:6.1.0.202203080745-r, perhaps due to some creative use of <repositories>?)