|
||||||||
|
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-14394) The version 1.... [email protected] (JIRA)
- [JIRA] (JENKINS-14394) The versi... [email protected] (JIRA)
- [JIRA] (JENKINS-14394) The versi... [email protected] (JIRA)
- [JIRA] (JENKINS-14394) The versi... [email protected] (JIRA)
- [JIRA] (JENKINS-14394) The versi... [email protected] (JIRA)
- [JIRA] (JENKINS-14394) The versi... [email protected] (JIRA)

That patch looks good, but upon applying it, I got the dreaded "ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job." message.
My repository looks like this:
remotes/target/HEAD -> target/master
remotes/target/changes/23/23/1
remotes/target/master
remotes/upstream/heads/master
The branch "target/changes/23/23/1" is supposed to be merged with "upstream/heads/master" before building. The repository got this way by specifying the same remote repo twice with two different refspecs.
I tried setting the "target branch" to "remotes/target/changes/23/23/1", "changes/23/23/1", and "refs/remotes/target/changes/23/23/1", and "target/changes/23/23/1". None worked.