Hi,
I am exploring the new Jenkins automated CD plugin release process for our plugin releases and have a few questions based on the documentation <https://www.jenkins.io/doc/developer/publishing/releasing-cd/>. I would appreciate any clarifications you can provide: *Q1. Release Triggering:* My understanding is that every successful build of the default branch triggers a release, meaning each release would be associated with only one PR (assuming it has the appropriate label). However, I noticed that in the kubernetes-plugin <https://github.com/jenkinsci/kubernetes-plugin/pull/1139/files>, the latest release includes changes from multiple PRs. How is this achieved? Also, does the release happen when the PR is merged? When the release happens is a bit unclear to me. *Q2. Automated Versioning:* How is the automated version generated? For a single PR with one commit, the version format seems to be *<some int>.<commit ID>*, as seen with the log-cli plugin version 40.934670f4a9b8 <https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/log-cli/40.934670f4a9b8/> triggered by a master push <https://github.com/jenkinsci/log-cli-plugin/commit/934670f4a9b84f243f8c0d9bbfc7be30a242e32b>. How is the version determined when multiple PRs or commits are involved? *Q3. PR Labels:* The labels added to PRs are crucial as they determine whether a release occurs. Is there any documentation specifying which labels trigger a release and which do not? Thank you for taking the time to provide your insights. Best regards, Vahila. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/0d811a10-809e-4c6e-9f3d-052b2773857en%40googlegroups.com.
