Testing jenkins-infra/pipeline-library#705

[jglick]

Checking jenkins-infra/pipeline-library#705. Need to verify

• that the head of this PR is deployed via ci.jenkins.io to incrementals: https://github.com/jenkinsci/jenkins-infra-test-plugin/runs/15400666853
• that after it is merged, the resulting master commit succeeds on ci.jenkins.io but does not deploy: https://github.com/jenkinsci/jenkins-infra-test-plugin/runs/15400717676
• that JEP-229 deployment to releases via GHA succeeds after that: https://github.com/jenkinsci/jenkins-infra-test-plugin/actions/runs/5682443987/job/15400837685#step:4:217
• that we have bits in the right Artifactory places: https://repo.jenkins-ci.org/incrementals/io/jenkins/plugins/jenkins-infra-test/148.v6fd424cf9948/ (6fd424c) vs. https://repo.jenkins-ci.org/releases/io/jenkins/plugins/jenkins-infra-test/149.v0b_d29a_e43f29/ (0bd29ae)

at which point

• this can be reverted to clean up: d0fbea8

[jglick]

Hmm, Incrementals deployment here happened before the build finished? How?

[jglick]

Oh https://ci.jenkins.io/job/Plugins/job/jenkins-infra-test-plugin/job/PR-98/1/ vs. https://ci.jenkins.io/job/Plugins/job/jenkins-infra-test-plugin/job/jglick-patch-1/1/

[jglick]

If you file a PR from an origin branch, Jenkins may temporarily create a non-PR build. Soon the branch project will be marked dead, but it seems ci.jenkins.io is not configured to immediately abort the running builds, which is an option. So jenkins-infra/pipeline-library#705 should help with that too—the branch build may run to completion, but will not deploy. Cannot test that with this PR since the branch project is already dead and not running any new builds.