#2249: change merging is no longer picking the newest change
-------------------+-----------------------
Reporter: dustin | Owner:
Type: defect | Status: reopened
Priority: major | Milestone: 0.8.7
Version: 0.8.6 | Resolution:
Keywords: |
-------------------+-----------------------
Comment (by dustin):
Based on {{{BuildRequest.mergeSourceStampsWith}}}, in the absence of
changes you'll get the sourcestamp of the first buildrequest handed to the
Build constructor, which based on my notes in comment 2 should give you
the first one sorted by submitted_at. Is that not what you're seeing?
Given the mystery above, we need more than "saw this too" to track this
one down, unfortunately.
--
Ticket URL: <http://trac.buildbot.net/ticket/2249#comment:6>
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
