Closed Bug 1498019 Opened Last year Closed Last year

Simplify logic around shipping phases and associated scopes.

Categories

(Firefox Build System :: Task Configuration, task)

task
Not set

Tracking

(firefox-esr60 fixed, firefox64 fixed)

RESOLVED FIXED
mozilla64
Tracking Status
firefox-esr60 --- fixed
firefox64 --- fixed

People

(Reporter: tomprince, Assigned: tomprince)

References

(Blocks 1 open bug)

Details

Attachments

(4 files)

No description provided.
The phase of a task doesn't depend on which phase graph it is being generated in.
- `beetmover-cdns should always use `:beetmover:action:push-to-releases`,
  not every task that happens to be part of the push graph.
- All other beetmover scopes only change depending whether the builds is
  a nightly build, or on a production branch.
These were originally built in the promotion phase because they are multi-l10n
builds and the L10n information wasn't stored in-tree. Now that the information
is in-tree, there is no reason to delay building them.
All the required on-push jobs will be pulled into the graph as dependencies.
The effect of this is to remove the upload symbols and generated sources tasks
from the release promotion graphs.
Attachment #9016085 - Attachment description: Bug 1498019: [release] Don't handle beetmover scopes by target task. → Bug 1498019: [release] Don't handle beetmover scopes by target task;
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/f970ec1fd696
[release] Don't set shipping phase based on target_tasks; r=aki
https://hg.mozilla.org/integration/autoland/rev/7e16cc9af2ba
[release] Don't handle beetmover scopes by target task; r=aki
https://hg.mozilla.org/integration/autoland/rev/70d26c3920b8
[release] Build fennec on-push, on release branches; r=aki
https://hg.mozilla.org/integration/autoland/rev/5341d78f8108
[release] Don't include on-push jobs in promote graph targets; r=aki
Depends on: 1501625
You need to log in before you can comment on or make changes to this bug.