Thanks Jesse for this links, very interesting. I like the idea that is proposed in JEP and even though I am a fan of GitOps, I think that in the current GH organisation plugin layout, the JEP #221 approach is a better first step. I would probably drop the customisation of the plugin versioning and enforce a standarization (gitflow, master branch) to ensure we have a common approach among all plugins.
As you mentioned, I suppose that I should not take the PoC setup to implement it in jira-plugin as it should be handled by the infra invisibly.. So as the status of this JEP is a proposal, what's the next step for making this happen? On Fri, Mar 27, 2020 at 9:22 PM Jesse Glick <[email protected]> wrote: > On Fri, Mar 27, 2020 at 3:32 PM Slide <[email protected]> wrote: > > There has been some discussion about automating plugin releases in the > past. > > https://jenkins.io/jep/221 > > and a working PoC > > https://github.com/jenkinsci/log-cli-plugin/tree/master/.github/workflows > > but for general usage we had discussed using a dedicated private > Jenkins server, not GitHub Actions. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/dNzLGbm36mQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0ctfepOARVexG2eNEAeE5SMe7-M1qWK8KrCzJS%3DDWuyQ%40mail.gmail.com > . > -- 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/CAPe2pWg2Lb1AVedzJnQRH4zJKCcJN9f6TKZwGrJ3-d687Rch%2Bw%40mail.gmail.com.
