#2000: "alwaysUseLatest" doesn't do what it says
--------------------------+--------------------
Reporter:  dabrahams      |       Owner:
    Type:  defect         |      Status:  new
Priority:  major          |   Milestone:  0.8.+
 Version:  0.8.4p1        |  Resolution:
Keywords:  git, projrepo  |
--------------------------+--------------------

Comment (by brendan):

 Is there a reason for the builder to override the branch for git when
 alwaysUseLatest is set? In git the revision is more precise than the
 branch, so when alwaysUseLatest isn't set, branch is meaningless. So it
 seems like the 'branch' field should override whatever's coming in from
 the build.

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2000#comment:4>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits

Reply via email to