Hello, I have Jenkins ver. 2.89.4 running on OSX Sierra 10.12.6
I have two GIT branches: 1. master 2. develop I have installed the maven release plugin into Jenkins and configured correctly the Jenkins paths for Java, Apache Maven, location of GIT executable. I have a simple project in maven (with POM files) that it has two simple modules, and when compiling with the command line MVN it works. Also when building it via Jenkins it is compiling. I have established the GIT connection into Jenkins job (maven job) and added to my project POM files the SCM(connection, developerConnection, url, tag) + distributionManagement to my local folder (I didn`t putted other GIT repo because I had some connection/auth issues.., but this is not important). The SCM connection to GIT works via HTTPS with settings.xml (user/pass) file and in the Jenkins console this part works (the SSH I`m not sure why it does not work.. even if the SSH is installed and setup correctly and from the mac terminal the git -T URL works with auth success, I think is related to the fact that Jenkins use a different mac account which is weird.., but again, this is not important because the SCM>HTTPS works so it is ok). >From the Jenkins job, the source management is set to develop, build triggers Build whenever a SNAPSHOT dependency is built > true, Poll SCM > true Build Environment > Maven release build > true with "Release goals and options" > -Dresume=false release:prepare release:perform and "DryRun goals and options" > -Dresume=false -DdryRun=true release:prepare Build > Root POM = "pom.xml", "Goals and options" > deploy scm:tag When I`m doing from "Perform Maven Release" for a maven release build (the installed maven plugin into Jenkins), it is incrementing the snapshot version from the develop repo and it is adding also the TAG version which is good. *BUT I will need before incrementing the snapshot version from the develop repo, if the build is success, I will need the current version merged to master repo (+adding the TAG).* Example: develop has 2.0.1-SNAPSHOT master has 2.0.0 Steps: build develop, if success, merge develop to master with version 2.0.1 (Without SNAPSHOT), then add the TAG version to master, then increment the develop version to 2.0.2-SNAPSHOT, and commit to develop. PS: I`ve attached the POM file here Thank you very much in advance! Best regards, Cotfas Vlad Nicolae -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4e0a036e-0cc0-474b-ad26-3d4a2d7dada7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
POM file.xml
Description: XML document
