[JIRA] [git] (JENKINS-22319) Referencing a purely local git branch breaks checkout
Ben Cooksley commented on JENKINS-22319 Referencing a purely local git branch breaks checkout Thanks for implementing the change - it is much appreciated. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22319) Referencing a purely local git branch breaks checkout
Mark Waite resolved JENKINS-22319 as Fixed Referencing a purely local git branch breaks checkout 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22319) Referencing a purely local git branch breaks checkout
Mark Waite closed JENKINS-22319 as Fixed Referencing a purely local git branch breaks checkout That sample script should NOT be considered as worthy of duplicating by anyone. I don't think there are many cases where a purely local jenkins branch is needed, with no intent to ever push the changes on that branch elsewhere. Change By: Mark Waite (02/Apr/14 9:31 PM) Status: Resolved Closed 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22319) Referencing a purely local git branch breaks checkout
Mark Waite commented on JENKINS-22319 Referencing a purely local git branch breaks checkout I would prefer that the case of "refs/" should always be considered properly qualified. My apologies that it worked before and regressed. One of the challenges of not having enough tests is that we can lose functionality through regressions. If you submit a pull request to consider "refs/" to always be properly qualified, please also submit a test which asserts that it works. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22319) Referencing a purely local git branch breaks checkout
Mark Waite updated JENKINS-22319 Referencing a purely local git branch breaks checkout Change By: Mark Waite (27/Mar/14 11:43 PM) Summary: UpdatingGitplugincausesexistingbuildstoimmediatelyfail Referencingapurelylocalgitbranchbreakscheckout 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22319) Referencing a purely local git branch breaks checkout
Ben Cooksley commented on JENKINS-22319 Referencing a purely local git branch breaks checkout The workspace is created before the Pre-SCM plugin executes, so the build never fails. If no pre-existing clone exists our script will make one as needed (it also knows the repository URL). An extreme pity this is seen as a special case considering it worked perfectly fine in the past. I see two possible solutions: 1) Have an absolute last resort possibleQualifiedBranches entry of singleBranch - ie. totally unmodified from the specification passed to it in the build configuration. 2) Consider the case of "refs/*" to always be properly qualified. Which one do you prefer? 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
