On Tue, Nov 9, 2021 at 3:06 PM José Lamas Ríos <[email protected]> wrote:
> Regarding 'conceptually compatible' I'm not sure whether you refer to >> automatic deployment in general or to the way it's implemented in this case >> > Well, any scheme by which the update center pattern-matches on plugin version numbers. I think the most natural way to support JEP-229 in the experimental update center would be: - Give `jenkins-maven-cd-action` an option to leave releases in draft after deployment. - Patch `isAlphaOrBeta` in the UC code to look for a GitHub release matching the version number of the plugin. If it exists, and it is currently in draft, treat the plugin like it is beta. Then if you enabled CD on your plugin and enabled the new option, your workflow would be - Merge a PR with an appropriate label. - Within the hour, it should appear on the experimental, but not regular, UC. - Collect feedback from beta testers, pushing fixes or unrelated changes as you like. - Whenever you are satisfied that a particular version (might have to be latest?) is safe, mark its release as ready in GitHub. - It should then soon appear on the regular UC. (Anyone who already has it will not see an upgrade—the bits are unmodified.) The first patch I could do pretty easily, if someone wanted to pick up the second patch. Looks like there is some GraphQL that could probably be extended, assuming Releases is supported. -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr30oMUsD1mkvzAJM85MQA4vfejTL2qf7fs3tFQpxhs%2Bug%40mail.gmail.com.
