Re: Applying Jenkins build number
Why not just update the pom (but not commit to scm) with a step like mvn versions:set -DnewVersion=$newVersion ? And newVersion you would parse from the pom file and add ${build.number} to it. /Anders On Thu, Nov 22, 2018 at 12:14 PM Jochen Wiedmann wrote: > Hi, > > when running Maven outside of Jenkins, I have the version number (for > example) 1.2, which is just fine. However, within Jenkins I'd like > that to be 1.2.${build.number}. Is that possible without overwriting > the version number in the pom with every build? For example, by using > a "jenkins" profile, which overwrites the project version somehow? > > Thanks, > > Jochen > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Applying Jenkins build number
The new way to deal with such situation is described here: https://maven.apache.org/maven-ci-friendly.html 0-SNAPSHOT 1.2.${revision} and let Jenkins run Maven like this mvn deploy -Drevision=${env.BUILD_NUMBER} (or maybe just $BUILD_NUMBER depending on the way you run Jenkins) -- Sent from: http://maven.40175.n5.nabble.com/Maven-Users-f40176.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Applying Jenkins build number
Hi, On 22/11/18 22:24, Francois MAROT wrote: The new way to deal with such situation is described here: https://maven.apache.org/maven-ci-friendly.html 0-SNAPSHOT 1.2.${revision} and let Jenkins run Maven like this mvn deploy -Drevision=${env.BUILD_NUMBER} (or maybe just $BUILD_NUMBER depending on the way you run Jenkins) Please add the configuration for flatten-maven-plugin to your configuration as described on the mentioned page... Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Applying Jenkins build number
You can also use jgitver (https://jgitver.github.io/) that was demoed at Devoxx this year to compute automatically the project version, even for each commit. Using a jgitver configuration of false true true You can get the versions computed for each commit, for example 1.2.0-1, 1.2.0-2, 1.2.0-3 Matthieu On Fri, Nov 23, 2018 at 6:54 AM Karl Heinz Marbaise wrote: > Hi, > > On 22/11/18 22:24, Francois MAROT wrote: > > The new way to deal with such situation is described here: > > https://maven.apache.org/maven-ci-friendly.html > > > > > > 0-SNAPSHOT > > > > > > 1.2.${revision} > > > > and let Jenkins run Maven like this mvn deploy > > -Drevision=${env.BUILD_NUMBER} (or maybe just $BUILD_NUMBER depending on > the > > way you run Jenkins) > > Please add the configuration for flatten-maven-plugin to your > configuration as described on the mentioned page... > > Kind regards > Karl Heinz Marbaise > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
RE: Applying Jenkins build number
cool -Original Message- From: Matthieu BROUILLARD Sent: Freitag, 23. November 2018 15:08 To: users@maven.apache.org; i...@soebes.de Subject: Re: Applying Jenkins build number You can also use jgitver (https://jgitver.github.io/) that was demoed at Devoxx this year to compute automatically the project version, even for each commit. Using a jgitver configuration of false true true You can get the versions computed for each commit, for example 1.2.0-1, 1.2.0-2, 1.2.0-3 Matthieu On Fri, Nov 23, 2018 at 6:54 AM Karl Heinz Marbaise wrote: > Hi, > > On 22/11/18 22:24, Francois MAROT wrote: > > The new way to deal with such situation is described here: > > https://maven.apache.org/maven-ci-friendly.html > > > > > > 0-SNAPSHOT > > > > > > 1.2.${revision} > > > > and let Jenkins run Maven like this mvn deploy > > -Drevision=${env.BUILD_NUMBER} (or maybe just $BUILD_NUMBER depending on > the > > way you run Jenkins) > > Please add the configuration for flatten-maven-plugin to your > configuration as described on the mentioned page... > > Kind regards > Karl Heinz Marbaise > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Applying Jenkins build number
I believe I came up with a simple solution: My POM now looks like my.group.id ${revision} my-artifact-id 1.2${build.number} So, ${build.number} is empty by default, unless in Jenkins, where I define it as ".${env.BUILD_NUMBER}". Jochen On Thu, Nov 22, 2018 at 12:19 PM Anders Hammar wrote: > > Why not just update the pom (but not commit to scm) with a step like > mvn versions:set -DnewVersion=$newVersion > ? > > And newVersion you would parse from the pom file and add ${build.number} to > it. > > /Anders > > On Thu, Nov 22, 2018 at 12:14 PM Jochen Wiedmann > wrote: > > > Hi, > > > > when running Maven outside of Jenkins, I have the version number (for > > example) 1.2, which is just fine. However, within Jenkins I'd like > > that to be 1.2.${build.number}. Is that possible without overwriting > > the version number in the pom with every build? For example, by using > > a "jenkins" profile, which overwrites the project version somehow? > > > > Thanks, > > > > Jochen > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Applying Jenkins build number
Fine that you found your way. The only issue with the technics relying on injection of some external value is that they make your build not reproducible. It might not be an issue if those injections are only for intermediate builds and that you tag your build at some point in time with real X.Y.Z version. By jgitver and purely the git information (tags, commits, branches) your intermediate buillds can be reproducible even later if you checkout later on. On Fri, Nov 23, 2018 at 10:08 PM Jochen Wiedmann wrote: > I believe I came up with a simple solution: My POM now looks like > > my.group.id > ${revision} > my-artifact-id > > > 1.2${build.number} > > > So, ${build.number} is empty by default, unless in Jenkins, where I > define it as ".${env.BUILD_NUMBER}". > > Jochen > > On Thu, Nov 22, 2018 at 12:19 PM Anders Hammar wrote: > > > > Why not just update the pom (but not commit to scm) with a step like > > mvn versions:set -DnewVersion=$newVersion > > ? > > > > And newVersion you would parse from the pom file and add ${build.number} > to > > it. > > > > /Anders > > > > On Thu, Nov 22, 2018 at 12:14 PM Jochen Wiedmann < > jochen.wiedm...@gmail.com> > > wrote: > > > > > Hi, > > > > > > when running Maven outside of Jenkins, I have the version number (for > > > example) 1.2, which is just fine. However, within Jenkins I'd like > > > that to be 1.2.${build.number}. Is that possible without overwriting > > > the version number in the pom with every build? For example, by using > > > a "jenkins" profile, which overwrites the project version somehow? > > > > > > Thanks, > > > > > > Jochen > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >