[
https://issues.jenkins-ci.org/browse/JENKINS-10483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158645#comment-158645
]
Chris Rode commented on JENKINS-10483:
--------------------------------------
"origin/release/XXX" worked for me. I had to ensure that the "Name of
repository" section in advanced was origin as well though
> Git plugin does not handle git-flow style feature branches (e.g.
> feature/myfeature) correctly
> ---------------------------------------------------------------------------------------------
>
> Key: JENKINS-10483
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10483
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Affects Versions: current
> Environment: Running on a Debian 6.0 virtual machine (Xen), Tomcat 6
> (from tomcat6 .deb package), Sun JDK 1.6.0_26 (from sun-java6-jdk .deb
> package), git 1.7.2.5
> Reporter: Lee Rosen
> Assignee: abayer
>
> When I configure a job to use a branch in the form feature/myfeature (as
> would be created by git-flow when starting a feature branch) the checkout in
> the workspace ends up being from the master branch after the job runs. The
> feature/myfeature branch is present on the git server pointed to by the URL
> configured in the job and can be successfully checked out into the workspace
> manually using the configured credentials. Further, configuring other simple
> branch names, like develop, as the branch in the job configuration works
> fully as expected -- only branch names beginning with 'feature/' seem to
> encounter a problem.
--
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
