The default bug view has changed. See this FAQ.

Add sendchange schedulers for update_shipping and postrelease builders so that shipit can trigger them

RESOLVED WONTFIX

Status

Release Engineering
Release Automation
RESOLVED WONTFIX
3 years ago
2 years ago

People

(Reporter: zeller, Assigned: zeller)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

3 years ago
Implement a new Builder that will run pushsnip and hook it and the existing postrelease builder up to their own Schedulers that can be triggered through SendChange. This sendchange is triggered by a button added to shipit.
(Assignee)

Updated

3 years ago
Assignee: nobody → johnlzeller
(Assignee)

Updated

3 years ago
Blocks: 1062205
(Assignee)

Comment 1

3 years ago
Based on our conversation last week, it sounds like a new builder is not needed for pushsnip, because it could be added to an existing Builder. I am unfamiliar with creating either Builders or Schedulers. Where do I start with these? Any clues?
Flags: needinfo?(rail)
I was thinking about integrating it into http://hg.mozilla.org/build/buildbotcustom/file/a106a8bf939a/process/release.py#l1225 to run an extra ssh command, similar to http://hg.mozilla.org/build/buildbotcustom/file/a106a8bf939a/process/factory.py#l4478
Flags: needinfo?(rail)
We have an update_shipping builder which modifies the update rules in Balrog (next gen update server), which we can hook up here. pushsnip will be deprecated in the near future - release users move to Balrog later this month, ESR to follow after that. So we don't need a new builder, just some way to sendchange to to existing ones.
Summary: new Builder to run pushsnip and hook it and the existing postrelease builder up to their own Schedulers that can be triggered through SendChange for shipit → Add sendchange schedulers for update_shipping and postrelease builders so that shipit can trigger them
Bug 1118794 will obsolete this
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.