Plugin release automation

[scurvydoggo]

This enables automatic releases upon merge to master, with release note generation.

It follows the guide here: https://www.jenkins.io/doc/developer/publishing/releasing-cd/

Depends on: jenkins-infra/repository-permissions-updater#3451

Testing done

Submitter checklist

Beta Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[samrocketman]

Looks right to me. I see you also have a PR merged on jenkins-infra/repository-permissions-updater#3451

In the future, if you want to release you have two methods: manually trigger the workflow from GitHub actions; alternately, add enhancement label before merging a PR and upon merge it will create a release.

The continuous release is near instantaneous. There will no longer be a large 8-hour delay before releases publish to the JUC. So that you're aware, it's good to be sure a PR is release-ready before merging it (documentation, hopefully some tests, config migrations if any, etc).

[scurvydoggo]

Ok. So in order to test the pipeline, I'll merge this and see what happens. I expect this will publish a new version of this plugin which contains no actual changes, just a different number. However it would set the basis for future releases.

[scurvydoggo]

Good news, everyone!

It appears to have updated the drafted release. So the refactoring has preserved that behaviour.

I'm not quite sure how to trigger the release. I think I un-draft it? Or merge a PR with a enhancement or fix label? I need to understand that aspect. However I believe we are able to merge the other PR now and it will be appended to the release notes.