Closed
Bug 1429417
Opened 8 years ago
Closed 8 years ago
masterball should keep track of last push handled
Categories
(Localization Infrastructure and Tools :: Automation, enhancement)
Localization Infrastructure and Tools
Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Pike, Assigned: Pike)
References
Details
When the build master is stopped and restarted, it currently doesn't track where it needs to start off from.
We should set the last push we got in the db, and restart right after.
That way, we'd be OK if the automation instance gets restarted without the poller being down.
Icing on the cake if we'd be able to do this for successfully handled changes, so we'd even redo interrupted runs. It wouldn't hurt to have duplicate entries in the Run table, so that'd be fine.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → l10n
Assignee | ||
Comment 1•8 years ago
|
||
This is FIXED by
https://github.com/Pike/master-ball/commit/4c25aa3030f3e09f8d6325e80002bd2394ba0b29
https://github.com/Pike/master-ball/commit/f23dc950272180f37046f5401c042efd2fcfb872
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•