Add support for release-promotion (new system for releases) #764

Closed
whimboo opened this Issue Mar 7, 2016 · 7 comments

Projects

None yet

1 participant

@whimboo
Contributor
whimboo commented Mar 7, 2016

Bug 1118794 is the tracking bug for the new release promotion system for release builds. Mainly @rail is working on it. Together with him we have to find a way to listen for specific builds (en-US and locale repacks), so we can trigger our functional tests for releases.

Via bug 1253369 we are collecting ideas for possible routing keys of Mozilla Pulse messages. Until this has not been clarified this issue is blocked on it.

@whimboo whimboo self-assigned this Mar 9, 2016
@whimboo
Contributor
whimboo commented Mar 9, 2016

So RelEng turned on Release Promotion for the latest Firefox 46.0b1 candidate builds. As result our automation didn't process any of those builds due to change Mozilla Pulse notifications. Sadly we were not able to run any tests with Release Promotion ahead of time. :(

@kairo-at if QA wants to have results of our functional tests, you will have to trigger an ondemand_functional testrun for all the platforms and locales you are interested in.

So what we would need to get this fixed are two different Pulse listeners. One for en-US builds and another one for the locale repacks.

L10n repacks

This could rely on routing keys as send from TC like index.releases.v1.mozilla-beta.latest.firefox.latest.l10n.linux.#. Whereby I'm not sure if the builds would be already uploaded to the candidates folder at this step. @rail can you please clarify? IMHO we might have to wait for the beetmover tasks too which would be this task and produce routing keys like: index.releases.v1.mozilla-beta.latest.firefox.latest.beetmover.3.linux.

en-US builds

This is not that easy given that RelEng does no longer produce those builds. Instead they will be picked up from the last green build on mozilla-beta, and repacked for a release build. What we would need is a message when this build is available under the candidates folder. @rail mentioned beetmover tasks to me yesterday and as it looks like we want routing keys like index.releases.v1.mozilla-beta.latest.firefox.latest.beetmover.en_US.linux from this task.

Sadly all the beetmover tasks do not have any property.json file attached which we could use to identify the locales, branch, platform, version, and revision to test.

@rail can you please tell us more details?

@whimboo
Contributor
whimboo commented Mar 10, 2016

Just to update for beta releases on mozilla-beta you can find appropriate taskcluster tasks with the following filter set:

https://treeherder.allizom.org/#/jobs?repo=mozilla-beta&filter-searchStr=release&filter-tier=1&filter-tier=2&filter-tier=3&exclusion_profile=false&selectedJob=676273

Then just look for tasks in the Release group, and click on inspect Task. Via the link to the task graph you will find all necessary tasks for the specific release promotion task graph.

@whimboo
Contributor
whimboo commented Mar 10, 2016

So there is actually an ongoing discussion on bug 1253369. So we should have it at a single place and I will paste my remaining questions over there.

@rail rail referenced this issue in mozilla/releasetasks Mar 10, 2016
Merged

Specify build properties in extra #144

@whimboo
Contributor
whimboo commented Mar 10, 2016

@rail and I will work on a solution so we can have mozmill-ci working with release promotion for 46.0b2.

@whimboo
Contributor
whimboo commented Mar 17, 2016

I got everything working locally now. Doing clean-up as next step and a PR should be up soon.

@whimboo whimboo removed the blocked label Mar 17, 2016
@whimboo whimboo added a commit to whimboo/mozmill-ci that referenced this issue Mar 17, 2016
@whimboo whimboo Add support for release-promotion messages (#764) 479050b
@whimboo
Contributor
whimboo commented Mar 17, 2016

PR #774 has been merged. I will make this alive on staging now and will push to production on Monday if no regression for daily builds are noticed over the weekend.

@whimboo whimboo closed this Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment