Confirmed users
4,467
edits
BugzillaAutoLanding: Difference between revisions
Jump to navigation
Jump to search
→BugzillaEventTrigger
| Line 174: | Line 174: | ||
==Component Descriptions and Implementation Notes== | ==Component Descriptions and Implementation Notes== | ||
===BugzillaEventTrigger=== | ===BugzillaEventTrigger=== | ||
We' | We're going to set up a scraper that will pull all bugs from bugzilla with whiteboard tags matching: | ||
[autoland-$branch] | |||
[autoland-$branch:$patchID:$patchID] | |||
Default behaviour would be to take [autoland-$branch] and grab all non-obsolete, non r- patches into the patchset that is then pushed to $branch, results returned and analyzed for further actions (like try->mozilla-{central,inbound}). To override or search for regressions we support adding explicit patchIDs to create a custom patchset for an autoland run. | |||
In a discussion with Mconnor, the suggestion for user interaction with autoland is to have radio buttons by each attachment (with a bit of select all/none js) so that you could pick your patches for autoland and have an input field & submit button to send something like: | |||
[autoland-try:1234:2345:3456] | [autoland-try:1234:2345:3456] | ||
[autoland-mozilla-inbound:1234] | [autoland-mozilla-inbound:1234] | ||
to the queue which would signify the final push destination and the attachment ids to use for the patch set. | to the queue which would signify the final push destination and the attachment ids to use for the patch set. Whether this is something we can do with Bugzilla would need investigating so at first we are implementing this with whiteboard tags & polling with the bugzilla API for these tags. | ||
===HgPusher=== | ===HgPusher=== | ||