[JIRA] (JENKINS-15830) Error: Unable to infer the new branch name from XXX

2012-11-14 Thread alex.ouzou...@me.com (JIRA)














































Alex Ouzounis
 updated  JENKINS-15830


Error:  Unable to infer the new branch name from XXX
















Change By:


Alex Ouzounis
(14/Nov/12 9:17 PM)




Description:


The problem lies in the fact that the plugin tries to deduce the branch to be
 create
 created
 absolute path from the current trunk path.The assumption is that the svn repository is using the following convention:http://svnserver.com/projectName and within that you have a a trunk and a branches folder.Our setup uses a completely different structure where the "trunk" folder is at the root and has a different name other than trunk. Within that "trunk" folder you have another 2 layers at least till you reach the project that has been checked out. trunk example: http://svnserver.com/FolderTrunk/Folder2/Folder3/Folder4/ProjectNamebranch example: http://svnserver.com/FolderBranches/Folder2/..At_Least_3_Folders../FeatureBranchThe "culprit" seems to be: svnmerge-plugin / src / main / java / jenkins / plugins / svnmerge / IntegratableProjectAction.javaA possible fix would be to also allow the user to define the full feature branch path from the root of the svn as an additional feature. That would allow us to create a feature branch anywhere within our svn structure since features branches can go in more than one "branch locations" (ie you have no way to automatically deduce the full branch path)Its not critical but currently we cannot use this plugin due to this problem.I have never developed for Jenkins but I am a Java Developer so I could give it a go myself as long as I am pointed in the right direction.



























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






[JIRA] (JENKINS-15830) Error: Unable to infer the new branch name from XXX

2012-11-14 Thread alex.ouzou...@me.com (JIRA)














































Alex Ouzounis
 created  JENKINS-15830


Error:  Unable to infer the new branch name from XXX















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Components:


svnmerge



Created:


14/Nov/12 9:16 PM



Description:


The problem lies in the fact that the plugin tries to deduce the branch to be create absolute path from the current trunk path.

The assumption is that the svn repository is using the following convention:

http://svnserver.com/projectName and within that you have a a trunk and a branches folder.

Our setup uses a completely different structure where the "trunk" folder is at the root and has a different name other than trunk. Within that "trunk" folder you have another 2 layers at least till you reach the project that has been checked out. 

trunk example: 
http://svnserver.com/FolderTrunk/Folder2/Folder3/Folder4/ProjectName

branch example: 
http://svnserver.com/FolderBranches/Folder2/..At_Least_3_Folders../FeatureBranch

The "culprit" seems to be: svnmerge-plugin / src / main / java / jenkins / plugins / svnmerge / IntegratableProjectAction.java

A possible fix would be to also allow the user to define the full feature branch path from the root of the svn as an additional feature. That would allow us to create a feature branch anywhere within our svn structure since features branches can go in more than one "branch locations" (ie you have no way to automatically deduce the full branch path)

Its not critical but currently we cannot use this plugin due to this problem.

I have never developed for Jenkins but I am a Java Developer so I could give it a go myself as long as I am pointed in the right direction.




Environment:


Jenkins Master on Ubuntu 12.04 




Project:


Jenkins



Labels:


plugin
svnmerge
error,




Priority:


Minor



Reporter:


Alex Ouzounis

























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