ci.j.io plugin jobs don't trigger on branch scan

[daniel-beck]

Service(s)

ci.jenkins.io

Summary

https://ci.jenkins.io/job/Plugins/ is configured with the "Suppression strategy" of "For matching branches suppress builds triggered by indexing (continue to honor webhooks)".

As a result, https://ci.jenkins.io/job/Plugins/job/disable-job-button-plugin/job/main/ was created but never triggered a build. In my case I even tried to be clever and integrated JEP-229 enablement into the initial commit, and CD doesn't work without a ci.j.io success status, so this was a release blocker until I (as Jenkins admin) triggered a build manually. The vast majority of maintainers lack the permissions to kick off builds.

It's unclear why this value is set the way it is. Comments in #3492 note that it was configured, while earlier advice in #3474 from Jesse indicates it may prevent a reconfiguration build storm and suggests its use temporarily. That was more than a year ago.

Reproduction steps

No response

[dduportal]

Ack, starting reconfiguration

[dduportal]

Setting applied, no rescanning :success:

[dduportal]

[timja]

your screenshot wasn't saved @dduportal not fully clear what's been done here

[dduportal]

[dduportal]

your screenshot wasn't saved @dduportal not fully clear what's been done here

Sorry, GitHub did behave weirdly. So I've set up the "Automatic triggering" of the GH org "Plugins" to suppress nothing has per the above screenshot.