m2 release plugin versioning policy
Hilikus
It looks like the current behaviour when doing a maven release from jenkins in a multi-module project is to assign the version specified in the web ui of jenkins to ALL the submodules
e.g in a project like this
1.0.0-SNAPSHOT (A)
|...1.0.0-SNAPSHOT (A1)
|...2.3.0-SNAPSHOT (A2)
if I specify in the ui that the version of the root pom (A in my example) should be 1.0.0 then even the second submodule (2.3.0-SNAPSHOT) will be released with version 1.0.0, probably due to the -B -DreleaseVersion arguments combo. Is there any way to change this behaviour? what I want is to release A1=1.0.0, A2=1.0.0 and A3=2.3.0
I see a "default versioning mode" in the configuration that seems to do just that; however, 1) it never keeps its state, whatever I change it to, it goes back to none 2) it doesn't even look like the actual behaviour is none, since none seems to be what I want. The behaviour I see is "specify one version for all modules"
I'm using m2release 0.10 and jenkins 1.460
Thank you
James Nord (jnord)
If you require that functionality you will need to downgrade to an earlier version (I think 0.7.1).
The functionality will be coming back but I have no current ETA.
See https://issues.jenkins-ci.org/browse/JENKINS-11466
/James
--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hilikus
How complex are the changes? could someone without jenkins plugin experience do it in a couple of days? it sounds to me like just a matter of constructing the correct command line invocation
James Nord (jnord)
From: Hilikus [mailto:thehi...@gmail.com]
Sent: 17 May 2013 18:57
To: jenkins...@googlegroups.com
Cc: James Nord (jnord)
Subject: Re: m2 release plugin versioning policy
when you say it will be coming back you mean what? being able to set a different version in the UI for each submodule
[JTN] Yes
or letting maven decide based on the SNAPSHOT version in the pom?
[JTN] if the issues with it can be worked out – and I think I have a plan.
or both?
[JTN] the individual one first, if the plan for using maven works, then using maven will be done after (or possibly at the same time).
How complex are the changes?
For the prompt the user – not very, it’s a buncy of Jelly config and moving some parameters around (and checking that no new modules have been introduced since the last build)
could someone without jenkins plugin experience do it in a couple of days?
[JTN] I would think so – the code did exist and was removed – so there is already some guidance on how to do this.
it sounds to me like just a matter of constructing the correct command line invocation
[JTN] that’s the easy bit (assuming you’re not on windows and don’t blow the command line argument length!). You need to store the variables in a the Action and get them from the post, and have the UI prompt for them.
On Friday, 17 May 2013 12:02:06 UTC-4, James Nord (jnord) wrote: