|
|
Line 16: |
Line 16: |
| == How do I claim a rentable project branch? == | | == How do I claim a rentable project branch? == |
| See [[ReleaseEngineering/DisposableProjectBranches#BOOKING_SCHEDULE]] | | See [[ReleaseEngineering/DisposableProjectBranches#BOOKING_SCHEDULE]] |
|
| |
| == Marking jobs as complete in the buildbot database ==
| |
| Sometimes we get a commit with a weird char or charset in the commit message. This can sometimes cause scheduling to get stuck when buildbot hits an exception.
| |
|
| |
| In general, you shouldn't need to remove the job or sourcestamp. It's much simpler to simply mark the request and buildset as complete. Here's an example:
| |
|
| |
| # Setting results == 4 allows us to search for records changed this way.
| |
| use buildbot_schedulers
| |
| set @REVISION='e87f642fa4a9'
| |
| update buildrequests set complete_at=UNIX_TIMESTAMP(),complete=1,results=4 \
| |
| where buildsetid in (select id from buildsets where sourcestampid in \
| |
| (select id from sourcestamps where revision like CONCAT(@REVISION,'%'));
| |
| update buildsets set complete_at=UNIX_TIMESTAMP(),complete=1,results=4 \
| |
| where sourcestampid in \
| |
| (select id from sourcestamps where revision like CONCAT(@REVISION,'%'));
| |
|
| |
|
| = Re-run jobs = | | = Re-run jobs = |