#2680: sourcestamp merging with no changes uses revision of oldest instead of
newest
--------------------+-----------------------
Reporter: brendan | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: 0.8.5 | Keywords:
--------------------+-----------------------
SourceStamp.mergeWith uses the revision of the first sourcestamp rather
than the last. If the sourcestamps don't carry changes, this means that a
builder will build the oldest of the merged revisions instead of the
newest. This doesn't seem expected or desired. I've attached a patch
(against 0.8.5 but it doesn't look like this has changed) to get what I
believe is the desired behaviour.
--
Ticket URL: <http://trac.buildbot.net/ticket/2680>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
