See https://wiki.mozilla.org/BugzillaAutoLanding for details and objects/tables We'll use this to keep track of any pushes that are currently being run which were triggered by the autoland system and once the autoland cycle for a push is complete it no longer needs to be in this db. The schedulerdb and the bug will be the permanent record for the push.
In terms of setting this up - you can work locally as we pull all the components together and get a staging env. set up. The deiverable for this bug should be an sql file that we can land which will set up the db & tables needed.
(In reply to comment #1) > The deliverable, even > that we can land (in hg.m.o/build/...)
This is currently implemented and has been in working condition for a fair amount of time. Next action is to have the database store a full history of landings.
Created attachment 618372 [details] [diff] [review] Completed Table v1 Add a table to hold completed jobs. This also stores a status field to inform of the termination status of the job.
Comment on attachment 618372 [details] [diff] [review] Completed Table v1 nice. my only concern, for longevity, is that this is a sqlite db - so perhaps we could have a cronjob that does regular backups of this file?
Found in triage.
This is implemented in the new version.