Issue Type: Bug Bug
Affects Versions: current
Assignee: Nicolas De Loof
Components: git-client
Created: 24/Dec/13 6:45 AM
Description:

Git client fails to parse branch refs with slashes. I have branch names with refs of the format refs/server/branch on the server which Jenkins pulls from creating refs/remotes/origin/server/branch in the Jenkins workspace. I do this so each user can push to a unique branch on the git server and let Jenkins pull and merge them onto master. I updated Jenkins for the first time since August and found that the Jenkins Git client is now failing to pull new commits using my setup. It was working previously.

Console Output:
Fetching changes from the remote Git repository
Fetching upstream changes from user@server:/repo.git
Seen branch in repository origin/hathaway/master
Seen branch in repository origin/server/master
Seen branch in repository origin/jquery
Seen branch in repository origin/master
Seen branch in repository origin/stargazer/master
Seen 5 remote branches
Merging Revision 34ad23df34dbab725ba61856d542c83a4eba09b9 (origin/master, origin/stargazer/master, origin/server/master, origin/hathaway/master) onto /master using default strategy
FATAL: Command "git rev-parse /master^{commit}" returned status code 128:
stdout: /master^{commit}

stderr: fatal: ambiguous argument '/master^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...][<file>...]'

Environment: Ubuntu 13.04 (x64)
Jenkins 1.544
Project: Jenkins
Priority: Major Major
Reporter: Loren Lang
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to