Closed Bug 1244563 Opened 4 years ago Closed 4 years ago
reorganize releasetasks template generation logic
while extending releasetasks this week I noticed a few things: 1) currently we ignore things like `updates_enabled` and `push_to_candidates_enabled` for l10n based jobs while we abide by those conditions for enUS. This is because of the different style in release_graph.yml.tmpl. 2) we loop over the enUS platforms twice for beetmover and funsize based jobs because they are in two different template files. 3) sometimes we use en_US_config["platforms"] and sometimes we use enUS_platforms. Both of these derive from https://dxr.mozilla.org/build-central/source/tools/buildfarm/release/release-runner.py#176 I'm going to try reorganizing the layout so we adopt the style of l10n.yml.tmpl for enUS and combine all enUS based jobs into enUS.yml.tmpl. Then put the conditions mentioned above into each respective file.
ftr - I landed a patch that removes the recently removed enUS_platforms var from release-runner.py https://hg.mozilla.org/build/tools/rev/d7fd7e40dc1f
Attachment #8714614 - Flags: review+
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.