[ https://jira.codehaus.org/browse/MSITE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346150#comment-346150 ]
Dennis Lundberg commented on MSITE-712: --------------------------------------- Hi Martin We need to see more parts of the log to be able to help you. Specifically the Maven command line that Jenkins runs and the lines just before the part that you included, that shows what plugin has run. This issue is not related to the site plugin, but probably the release plugin. Do you use the release plugin? > maven-site-plugin generates incorrect git -tag command > ------------------------------------------------------ > > Key: MSITE-712 > URL: https://jira.codehaus.org/browse/MSITE-712 > Project: Maven Site Plugin > Issue Type: Bug > Components: multi module > Affects Versions: 3.3 > Environment: maven 3.0.2 > jdk 1.7 > Reporter: Martin Gainty > Priority: Trivial > > /*commit pom.xml */ > 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 > /*commit to 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 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://g...@github.com/{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 > /*-a, -s, and -u <key-id> are absent, -a is implied. so -a should have been > supplied but was not so we'll bypass this for now */ > /*<tagname> > The name of the tag to create, delete, or describe. The new tag name must > pass ALL checks defined by git-check-ref-format(1). Some of these checks may > restrict the characters allowed in a tag name. > */ > since tagname is missing > the generated git tag command doesnt know the name of what to commit to in > refs/tags/ > (refs/tags/$tagname is used unless -d/-l/-v is given to delete, list or > verify tags.) > temp workaround is to commit everything at command line to git > then use maven-site-plugin -- This message was sent by Atlassian JIRA (v6.1.6#6162)
