Jordan Lund (:jlund) Reporter
	Description • 7 years ago

+++ This bug was initially created as a clone of Bug #1405681 +++

like bug 1405681 we should first determine if we want this and if we do, generate them.

That means we do the work that was done in 1405681 and then:

update official rule 145 to point to Firefox-56.0.2-buildN-WNP
update rule current 56.0.1 rule 659 to Firefox-56.0.2-buildN-win64-migration-WNP

where rule 659 contains the required partial from this bug.

See https://docs.google.com/document/d/1_b3SuHiMZn141jM_MHw9sclm8nkn_COrlbHF44NIWKY/edit for more details

	Rail Aliiev [:rail] Assignee
	Comment 1 • 7 years ago

This is what I've done so far:
0) downloaded the original release blob (Firefox-56.0.2-build1)
1) In Balrog: updated the Firefox-56.0.2-build1 blob with the attached skeleton
2) Removed the update verify and push to cdns tasks starting from https://github.com/JohanLorenzo/win32-to-win64-partials/blob/528f5aa785385c6d872a259c383cf08e50b10e17/graph.yml.tmpl#L208
3) ran the graph generation
4) Downloaded Firefox-56.0.2-build1, edited its name in the file and set to 
Firefox-56.0.2-build1-win64-migration-WNP
5) updated the Firefox-56.0.2-build1 with one I originally downloaded in step 0) (reverted it in other words)


TODO:

1) Add Bouncer products for these MARs
2) set up the test channel rules to point to Firefox-56.0.2-build1-win64-migration-WNP. Likely we'll need to duplicate https://aus4-admin.mozilla.org/rules/659 to the test channels and adjust the priority and the mapping.
3) ask QE to verify the updates

	Rail Aliiev [:rail] Assignee
	Comment 2 • 7 years ago

FTR, the graph was https://tools.taskcluster.net/groups/EqvPP7K6TfSNolfLCw2_EQ

	Johan Lorenzo [:jlorenzo] - On PTO, back on September 11th
	Comment 3 • 7 years ago

Done:
1) Add Bouncer products for these MARs
2) Made https://aus4-admin.mozilla.org/rules/659 release only, instead of release*
3) Changed rules to migrate/show WNP:
   * Modified https://aus4-admin.mozilla.org/rules/627 (release-cdntest only) to point to 56.0-build6-bz2-WNP. Same thing was done on release-localtest, and will be done for release
   * Created https://aus4-admin.mozilla.org/rules/665 to migrate eligible users <56.0.1 (which means 56.0)  to 56.0.2, with WNP
   * Created https://aus4-admin.mozilla.org/rules/666 to show other users on 56.0 the WNP
   * https://aus4-admin.mozilla.org/rules/585 will upgrade users on 56.0.1 to 56.0.2 with neither migration nor WNP.

At the moment #665 and #666 are release-cdntest, but will eventually be release*

	Rail Aliiev [:rail] Assignee
	Comment 4 • 7 years ago

Apparently I didn't edit the templates to set to_mar to use win64. D'oh.

	Rail Aliiev [:rail] Assignee
	Comment 5 • 7 years ago

Repeated steps in comment 1 with the fixed template: https://tools.taskcluster.net/groups/YpslBhAOT9avCOQEGam3lg