#609: Have git checkout code in updated branch rather than in master.
-------------------+--------------------------------------------------------
Reporter: ktf | Owner: abyx
Type: defect | Status: closed
Priority: major | Milestone: 0.7.12
Version: 0.7.11 | Resolution: fixed
Keywords: |
-------------------+--------------------------------------------------------
Changes (by dustin):
* status: assigned => closed
* resolution: => fixed
Comment:
{{{
commit 2e875cedbcb52a0d85ce779131112c7db8abc664
Author: Aviv Ben-Yosef <[email protected]>
Date: Thu Dec 31 17:14:26 2009 +0200
Fixing ticket #609
The problem in the ticket is that Git does not checkout the wanted
branch, but simply checks out master branch and resets it to the HEAD of
the given branch. This means that any scripts in the build that rely on
the name of the git-branch in the repo will not see the name they expect
to see.
We do not want to simply checkout the branch every time, as that will
leave a lot of "dangling" branches if the branch names are changed with
time.
So, the decision is to do the same thing we did till now, but also add
a step for renaming the branch to the expected name, and make sure the
fetching will reset to the wanted revision.
}}}
--
Ticket URL: <http://buildbot.net/trac/ticket/609#comment:6>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
