[
https://issues.jenkins-ci.org/browse/JENKINS-9654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat resolved JENKINS-9654.
------------------------------
Resolution: Fixed
The issue at JFrog is said to be fixed:
https://issues.jfrog.org/jira/browse/HAP-181
So resolving this one as fixed.
> Hooks make staging impossible
> -----------------------------
>
> Key: JENKINS-9654
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9654
> Project: Jenkins
> Issue Type: Bug
> Components: artifactory
> Affects Versions: current
> Environment: Artifactory 2.3.3.1
> Jenkins: 1.410
> Windows server 2008
> Reporter: Mikael Floberg
> Assignee: yossis
>
> When i run the staging I get an error. this is becasue we have hooks in our
> subversion saying that we need to have a special text in the commit text.
> This makes the staging impossible for us. Is it possible to add textfields
> where you can add your comments to all the commits that are made?
> My log:
> 12:33:11 [INFO] BUILD SUCCESSFUL
> 12:33:11 [INFO]
> ------------------------------------------------------------------------
> 12:33:11 [INFO] Total time: 6 seconds
> 12:33:11 [INFO] Finished at: Wed May 11 12:33:11 CEST 2011
> 12:33:11 [INFO] Final Memory: 18M/62M
> 12:33:11 [INFO]
> ------------------------------------------------------------------------
> 12:33:11 channel stopped
> 12:33:11 [RELEASE] Creating subversion tag:
> https://subversion.xx.xx.fujitsu.com/svn/repository/xxx/xxx/alarmws/tags/alarmws-1.0-TESTAR
> 12:33:14 [RELEASE] Committing next development version
> 12:33:16 Failure in post build SCM action:
> org.tmatesoft.svn.core.SVNException: svn: Commit failed (details follow):
> 12:33:16 svn: 'pre-commit' hook failed with error output:
> 12:33:16 Committer: denmif
> 12:33:16 Commit message: "[artifactory-release] Committing next development
> version"
> 12:33:16 Commit rejected: No JIRA project key (e.g. APTEXAMPLES-123)
> detected in commit message.
> 12:33:16 svn: MERGE of /svn/repository/xxx/xxxx/alarmws/trunk: 409 Conflict
> (https://subversion.xx.xx.fujitsu.com)
> 12:33:16 [RELEASE] Reverting working copy:
> C:\Jenkins\jobs\Alarmws_-_Trunk\workspace\alarmws
> 12:33:17 [RELEASE] Reverting subversion tag:
> https://subversion.xx.xxx.fujitsu.com/svn/repository/xxx/xxx/alarmws/tags/alarmws-1.0-TESTAR
> 12:33:18 [RELEASE] Failed to revert
> 'https://subversion.xx.xx.fujitsu.com/svn/repository/xxx/xxx/alarmws/tags/alarmws-1.0-TESTAR':
> svn: 'pre-commit' hook failed with error output:
> 12:33:18 Committer: denmif
> 12:33:18 Commit message: "[artifactory-release] Reverting vcs tag:
> https://subversion.xxx.xx.fujitsu.com/svn/repository/xxx/xxx/alarmws/tags/alarmws-1.0-TESTAR";
> 12:33:18 Commit rejected: No JIRA project key (e.g. APTEXAMPLES-123)
> detected in commit message.
> 12:33:18 svn: MERGE of /svn/repository/xxxxx/xxxx/alarmws/tags: 409 Conflict
> (https://subversion.xx.xx.fujitsu.com)
> 12:33:18 Finished: FAILURE
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
