[PROPOSAL] Split js-libs repo in individual repos (one per module)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[PROPOSAL] Split js-libs repo in individual repos (one per module)

Victor Martinez
Hi there,

I've seen when using maven multimodes git repos in Jenkins plugins are mostly based on the same general versioning, such as the previous pipeline-pluginblueocean, but I've found a minor discrepancy in that particular assumption and it's about the js-libs.

This particular repo combine different plugins and each plugin is a maven module with a different version, for instance:
I'd like to purpose to standardise as individual git repos therefore their release lifecycle and versioning can be independent and also get the benefits of using different parent POM versions. I know it might be a bit of overwhelming work (git repos, move history, Jenkins pipelines...), and no idea how to proceed (maybe raising a jira ticket in case we agree) but IMO it's worth to keep some homogenous standard. What do you think? 

Cheers

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/82ccb4a1-ef4f-4e9d-8fd0-63984c6a6264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [PROPOSAL] Split js-libs repo in individual repos (one per module)

Jesse Glick-4
On Wed, Nov 29, 2017 at 6:47 AM, Victor Martinez
<[hidden email]> wrote:
> I'd like to purpose to standardise as individual git repos therefore their
> release lifecycle and versioning can be independent and also get the
> benefits of using different parent POM versions.

+1, makes sense. `maven-release-plugin` _can_ be run in subdirectories
but that is really not the conventional usage.

> I know it might be a bit of
> overwhelming work (git repos, move history, Jenkins pipelines...)

Probably not that hard. I would not bother moving history (i.e., `git
filter-branch` black magic) in this case, since there are only 126
commits, and the history is not all that interesting—it is not likely
someone three years from now is going to want to `git bisect` why some
version number was incremented in a `package.json`.

> no
> idea how to proceed (maybe raising a jira ticket in case we agree)

Probably just requires the usual `HOSTING` ticket if there is
consensus. Do you expect to help maintain this stuff? Adding Tom
Fennelly to CC.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr39S6foTNMjbatbvijTjMYd-teyo9ft%3DNQXd66ypw_ULQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: [PROPOSAL] Split js-libs repo in individual repos (one per module)

Victor Martinez
Awesome! I'm not really planning to do any maintenance though, let's see then what others think about this

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e08be7ac-0f1d-4fa3-ae62-3a468329187b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.