[PROPOSAL] Continuous Delivery of Jenkins Components

[Jesse Glick]

I have had this on the back burner for a while and just got around to
finishing the write-up. The core capability actually already works, if
a little crudely, but to be widely adopted we would need to implement
some infrastructure at the organization level to make it simple for
maintainers to set up.

https://github.com/jenkinsci/jep/pull/315

[Jesse Glick]

This is now JEP-229 and is basically implemented and working on two little plugins now. Are owners of components in @jenkinsci (not necessarily plugins…) interested in beta-testing?

https://github.com/jenkinsci/incrementals-tools#superseding-maven-releases

This is particularly pleasing in conjunction with GitHub’s new auto-merge feature, which you can enable as a repo owner as part of branch protection: you can prepare some change, file a PR for it with a meaningful title and a classification label like `feature`, click the button to auto-merge, and go to bed. If and when the Jenkins build passes, the PR will get merged to `master`. If and when the `master` build also passes, your component will be deployed, release notes will be created for you, and (in the case of a plugin) it will appear on the update center soon thereafter.

[Mark Waite]

I'd like to try it on the platformlabeler-plugin, though I won't have any time to investigate it for at least 10 days.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0XUo1_Nj1jm54AuofyKXxH%3DQMio31i-V5vyGMO4xKmQA%40mail.gmail.com.