[
https://issues.jenkins-ci.org/browse/JENKINS-10575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161792#comment-161792
]
Milutin Jovanovic commented on JENKINS-10575:
---------------------------------------------
A workaroung that works for me is to spacify two branches to build, first
master and then the one I actually want to build. Interestingly, only one
branch is built this way, the second one.
> git plugin does not support / in branch names
> ---------------------------------------------
>
> Key: JENKINS-10575
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10575
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Environment: git plugin 1.1.9, jenkins 1.423
> Reporter: Jørgen Tjernø
> Assignee: abayer
>
> To reproduce:
> * Set up a job that checks out a project from git
> * Set "Branches to build" specifier to {{something/somethingelse}} (that's
> valid in your git project)
> * Try to build
> This gives me the following error:
> {{ERROR: Couldn't find any revision to build. Verify the repository and
> branch configuration for this job.}}
> Doing the following makes the job build fine:
> * git checkout -b something-somethingelse something/something else
> * git push origin something-somethingelse
> * Set "Branches to build" specifier to {{something-somethingelse}}
--
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
