You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Esteban Porcelli (JIRA)" <ji...@codehaus.org> on 2013/04/26 15:49:53 UTC
[jira] (SCM-682) Maven release fails when releasing from a named
branch
[ https://jira.codehaus.org/browse/SCM-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Esteban Porcelli updated SCM-682:
---------------------------------
Attachment: maven-scm-provider-hg-SCM-682.patch
possible solution
> Maven release fails when releasing from a named branch
> ------------------------------------------------------
>
> Key: SCM-682
> URL: https://jira.codehaus.org/browse/SCM-682
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-mercurial (hg)
> Affects Versions: 1.7
> Environment: openSUSE 11.4 (x86_64)
> java version "1.6.0_26"
> Maven 3.0.4
> maven-release-plugin 2.3.2
> Hg version: 1.7.5
> Jenkins ver. 1.471
> Reporter: João Loureiro
> Attachments: maven-scm-provider-hg-SCM-682.patch
>
>
> When trying to build a release from a named branch, maven release plugin fails when trying to tag. The first character of the name of the branch appears to be trimmed for no apparent reason. (Some details omitted with '*'.)
> [workspace] $ /usr/bin/hg update --rev RELEASE_2.4
> (...)
> [INFO] [INFO] BUILD SUCCESS
> (...)
> [INFO] Checking in modified POMs...
> [INFO] EXECUTING: /bin/sh -c cd /var/lib/jenkins/jobs/******/workspace && hg branch
> [DEBUG] RELEASE_2.4
> [INFO] EXECUTING: /bin/sh -c cd /var/lib/jenkins/jobs/******/workspace && hg outgoing
> [INFO] EXECUTING: /bin/sh -c cd /var/lib/jenkins/jobs/******/workspace && hg commit --message '[maven-release-plugin]' (files ommitted)
> [DEBUG] No username found, using '******' instead
> [INFO] EXECUTING: /bin/sh -c cd /var/lib/jenkins/jobs/******/workspace && hg push ssh://******//home/hgroot/******/
> [DEBUG] pushing to ssh://******//home/hgroot/******/
> [DEBUG] searching for changes
> [DEBUG] remote: adding changesets
> [DEBUG] remote: adding manifests
> [DEBUG] remote: adding file changes
> [DEBUG] remote: added 1 changesets with 19 changes to 19 files
> [INFO] Tagging release with the label ******...
> [DEBUG] ScmTagPhase :: scmTagParameters remotingTag true
> [DEBUG] ScmTagPhase :: scmTagParameters scmRevision null
> [DEBUG] ScmTagPhase :: fileSet basedir = /var/lib/jenkins/jobs/******/workspace; files = []
> [INFO] EXECUTING: /bin/sh -c cd /var/lib/jenkins/jobs/******/workspace && hg tag --message '[maven-release-plugin] copy for tag ******' ******
> [DEBUG] No username found, using '******' instead
> [INFO] EXECUTING: /bin/sh -c cd /var/lib/jenkins/jobs/******/workspace && hg branch
> [DEBUG] RELEASE_2.4
> [INFO] EXECUTING: /bin/sh -c cd /var/lib/jenkins/jobs/******/workspace && hg outgoing
> [WARNING] A different branch than ELEASE_2.4 was found in outgoing changes, branch name was RELEASE_2.4. Only local branch named ELEASE_2.4 will be pushed.
> [INFO] EXECUTING: /bin/sh -c cd /var/lib/jenkins/jobs/******/workspace && hg push -rELEASE_2.4 ssh://******//home/hgroot/******/
> [DEBUG] pushing to ssh://******//home/hgroot/******/
> [DEBUG] abort: unknown revision 'ELEASE_2.4'!
> [ERROR]
> EXECUTION FAILED
> Execution of cmd : push failed with exit code: 255.
> Working directory was:
> /var/lib/jenkins/jobs/******/workspace
> Your Hg installation seems to be valid and complete.
> Hg version: 1.7.5 (OK)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira