In the case of multi project layout, more than a matter of personal taste, it can depends on how much related the subprojects are: look at this question that refers to the CollabNet Subversion blog.

I agree that it's common to have the feature branch name at the of the URL, so I suggest to support these kind of URLs in addition to that listed above:

Upstream SVN URL Branch SVN URL(default)
http://svnserver/project/trunk/subproject http://svnserver/project/branches/feature/subproject
http://svnserver/project/branches/feature/subproject http://svnserver/project/branches/anotherfeature/subproject

This lead to have the feature branch creation form a little bit more complex, but this way we'll be able to handle the three cases:

  • single project layout
  • multi project layout with non-related projects or loosely-related projects
  • multi project layout with closely related project
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to