FTR, there was a thread about the next steps for XTrigger lib: https://groups.google.com/forum/#!searchin/jenkinsci-dev/XTrigger%7Csort:date/jenkinsci-dev/voKBrqz7V_o/rCP5ysYZBwAJ AFAICT, we still need to get a release, and ownership has not been fully transferred to anyone. https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/component-xtrigger-lib.yml references only Gregory
Tony, if you are fine with that, we can just co-maintain the library for now. In my case I would rather want to help to get it over the line and to help with further releases if needed, I have no time to really "maintain" the component WDYT? On Thursday, July 11, 2019 at 11:48:45 AM UTC+2, Tony Noble wrote: > > I realise this isn't a plugin as such, so not sure how the process would > work. > > A number of trigger plugins, mine included (urltrigger) rely on > xtrigger-lib to perform the core job handling and cron scheduling. From > what I can see, Gregory Boissinot used to maintain this, along with the > dependent plugins, but I'm guessing he stepped back from them all at the > same time. > > At the moment, a number of issues within xtrigger-lib prevent the > dependent plugins from being pipeline-compliant. Proposed fixes for them > have been merged by @oleg-nenashev , but no release has been performed, so > they're not specifically useable. > > I guess the questions is - how do I go about getting a release created? > I'm happy to take the responsibility on myself, if that's what's required, > but as mentioned above, I'm not sure how the process would work for a lib > rather than a plugin. > > Tony > -- 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/edb112a3-84f7-4acf-8581-ccff5caf4cdf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
