Which version of the maven release plugin are you using? I'd check with at least 2.4.2 or 2.5 since known issues with Git have been fixed in those versions. Le 13 mai 2014 03:07, "Neil Hunt" <[email protected]> a écrit :
> For some reason, when running maven release, it is giving me an invalid > URL just for the tagging part of the push. For the pom.xml commit/push, it > works fine and goes to appropriate URL. See below: > > > > [INFO] Working directory: /opt/jenkins-home/jobs/Section > 4362/workspace/section4362-parent > > [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section > 4362/workspace/section4362-parent" && git commit --verbose -F > /tmp/maven-scm-217365030.commit '/opt/jenkins-home/jobs/Section > 4362/workspace/section4362-services/pom.xml' > '/opt/jenkins-home/jobs/Section 4362/workspace/section4362-webapp/pom.xml' > '/opt/jenkins-home/jobs/Section 4362/workspace/section4362-static/pom.xml' > pom.xml > > [INFO] Working directory: /opt/jenkins-home/jobs/Section > 4362/workspace/section4362-parent > [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section > 4362/workspace/section4362-parent" && git symbolic-ref HEAD > [INFO] Working directory: /opt/jenkins-home/jobs/Section > 4362/workspace/section4362-parent > [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section > 4362/workspace/section4362-parent" && git push ssh:// > [email protected]/{org}/Section4362.git maven-release-test:maven-release-test > [INFO] Working directory: /opt/jenkins-home/jobs/Section > 4362/workspace/section4362-parent > [INFO] Tagging release with the label section4362-parent-0.3... > [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section > 4362/workspace" && git tag -F /tmp/maven-scm-882610155.commit > section4362-parent-0.3 > [INFO] Working directory: /opt/jenkins-home/jobs/Section 4362/workspace > [INFO] Executing: /bin/sh -c cd "/opt/jenkins-home/jobs/Section > 4362/workspace" && git push ssh://[email protected]/{org}section4362-parent-0.3 > [INFO] Working directory: /opt/jenkins-home/jobs/Section 4362/workspace > > You can see that for the push after the commit, it pushes to ssh:// > [email protected]/{org}/Section4362.git ({org} scrubbed by me), whereas for > the push after the tag, it goes to ssh://[email protected]/{org} - URL > should include /Section4362.git at the end. All my pom files specify the > correct: scm:git:ssh://[email protected]/{org}/Section4362.git > > How would URL be changing for tag push and where would it get it from? > Build is obviously failing at that step saying unable to connect to repo. >
