Mark Waite resolved Bug JENKINS-22319 as Fixed

The git-plugin 2.1.0 and git-client-plugin 1.7.0 combination now treat refs/heads/branch_name as a valid branch name if a local branch named "branch_name" exists. No requirement for a remote branch, and no requirement for a tracking branch.

Verifying this did require that I insert a pre-build step, and that I limit that pre-build step to only execute on Linux machines. The pre-build step I used was:

[ -d .git ] || git init
git checkout master || git checkout -b master -t origin/master
[ -d .git/objects/info ] || mkdir -p .git/objects/info
[ -f .git/objects/info/alternates ] || echo /var/cache/git/mwaite/skrooge.git/objects > .git/objects/info/alternates
git branch -D jenkins || git checkout -b jenkins a449a3e5a101623cdd70d9eecdbe0ca0335a86b3
git log -n 2

That set of steps include debug commands to help me diagnose the issue, and an attempt to persuade the system to use a local mirror as a reference repository. I don't know which (if any) of those steps are required or crucial for the "refs/heads/jenkins" will be honored.

Change By: Mark Waite (02/Apr/14 9:29 PM)
Status: Open Resolved
Resolution: Fixed
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/d/optout.

Reply via email to