I have to replace an existing plugin for the sole purpose of changing the
plugin Id. The following steps were suggested. I’m looking for feedback from
anyone who has done this in the past or if you see any potential problems with
these steps before I start the process.
Thanks.
1. Integrate
On Fri, Feb 21, 2020 at 9:50 AM Chris Kilding
wrote:
> Versions of each downstream plugin that is relevant to the use case would be
> pinned and controlled in the POM. Each meta-plugin release marks a
> combination of those plugins that are certified to work together. This takes
> the version t
This used to be done for pipeline with the 'workflow-aggregator' plugin,
afaik it's not very popular though? and isn't really being maintained
anymore
Any one able to provide any background? Or why this would be a good / bad
idea
Thanks
Tim
On Fri, 21 Feb 2020 at 14:50, Chris Kilding
wrote:
>
Hi Rick,
For specific use cases, perhaps we are looking more at meta-plugins than
metapackages…
Meta-plugins would consist (almost) exclusively of a POM. Versions of each
downstream plugin that is relevant to the use case would be pinned and
controlled in the POM. Each meta-plugin release mark
+1 for me for an extra release as well
--
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-dev+unsubscr...@googlegroups.com.
To view this discussion
+1 from me for an extra release.
On Thursday, February 20, 2020 at 1:47:40 AM UTC-7, Oleg Nenashev wrote:
>
> UPD: 2.221 was released by Kohsuke yesterday:
> https://jenkins.io/changelog/#v2.221
> This release is actually based on the Sunday's state of the master branch,
> so the release does no
>
> that said and switching topic slightly should we start releasing every
> change from master as a new version?
Once the core release automation project is completed, we can discuss
making the "weekly" releases more frequent.
Right now we are not in the position to do that
On Fri, Feb 21, 2020
o think it would be a shame to buy have these (disabled by default)
improvements available for experimenting with in the next LTS so I am plus one
for a mid week release.
that said and switching topic slightly should we start releasing every change
from master as a new version?
--
You received
+1 for the extra release. JEP-223 is really important.
On Fri, Feb 21, 2020 at 8:52 AM Angélique Jard wrote:
> +1 for the cut release, I would be very happy to see JEP-223 in the next
> LTS :)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developer
