1583685 - Automate stub installer work for partner respins

Status: NEW

(Release Engineering :: Release Automation, enhancement)

Description

[Nick Thomas [:nthomas] (UTC+12)]

Bug 1538995 added support for creating stub installers for partner repacks, and concentrated on the workflow for regular releases. Subsequently we've handled several new configurations or respins of existing ones, which require quite a bit of manual work to copy the files around, set up bouncer, and verify bouncer is working. We should automate this.

We'll need to

• [promote] hook up the release-partner-repack-bouncer-sub-firefox task to the promote_firefox_partners release flavour, so that it creates the appropriate products and locations
• [push] split out pushing files into firefox/releases/partners/ from the main firefox-push-to-release task into it's own, so it can be run separately
  • Use the existing partners parameter in the task payload to control which partners are copied
  • hook up the lambda function which clears the CDN cache to beetmover, so that we can overwrite files and not suffer a 1 week of stale files
• [push] figure out what to do about bouncercheck, this is missing from releases too
• [ship] split out the partner aliases work from the release-bouncer-aliases-firefox task into it's own, so it can be run separately
• determine if we with to proceed directly to a ship_firefox_partners flavour, since we need tasks that run in multiple phases. Is it OK to not stop for any human checks ? If so, set up dependencies so that works properly

Comment 1

[Aki Sasaki (not active)]

(In reply to Nick Thomas [:nthomas] (UTC+12) from comment #0)

• [promote] hook up the release-partner-repack-bouncer-sub-firefox task to the promote_firefox_partners release flavour, so that it creates the appropriate products and locations

Should just be adding it to rebuild_kinds. This looks like a good list, thank you!