1385996 - move releasestasks to in-tree scheduling

Status: RESOLVED DUPLICATE of bug 1397762

(Release Engineering :: Release Automation: Other, enhancement)

Description

[Kim Moir [:kmoir] ET]

On Friday I had a meeting with rail and catlee regarding migrating release tasks to in-tree scheduling.  Here are some notes

Scope:
Instead of release runner tagging bb trees and reconfiging to run a release, we would trigger a hook that is in tree.  Hook is not scheduled, run on demand.
Hooks can be triggered by release runner?

Implementation:
Can leave bb release jobs scheduled through bbb, priority is to get scheduling switched over
Test graph, sanity checks
Strip out release runner so all it does is invoke the job

Testing of graph generation, release sanity should be moved in tree 

Different buildid
No l10n from shipit bumper
Build number

Currently, no mechanism for shipit to map to tasks

How does decision task know version? Passed in parameters.yml
Dynamic env -> task
Variable to pass revision to use
Pass paramaters.yml
-add target to filter tasks to run

Depend on tasks from previous tasks

Relman - trigger release before builds are done
Previous task in target
Release graph - ci graph
Add graph -> new tasks

Like backfilling tests
Can’t backfill CoT/builds

Changeset in rr -> treeherder push -> taskgroup

Unique task ids -> in tree scheduling

Decision task.json
Funsize - move to in-tree scheduling

Priorities
1) Before implementing in tree releasetasks we should complete the remaining work so Fennec is on par with Firefox automation/release promotion
2) Releasetasks -> manual release runner doesn’t start it
In tree scheduling - reimplement graph, copy releasetasks, logic and templates go away

I'm going to do some further investigation on how this can be implemented, notes above are very rough.