749188 - carry forward reference to release manifest through entire release automation

Status: RESOLVED FIXED

(Release Engineering :: Release Automation: Other, defect, P3)

Description

[[e-mail] (:bhearsum)]

Currently, most builders require some sort of information fed to them about which release they're working on. In most cases, they receive a release tag. Once bug 748773 is resolved, we'll put all that release information in a common manifest. We need a way to carry forward that manifest name through the entire release automation, without requiring an initial reconfig.

A few us talked about this IRL a bit, and thought that we might be able to do it by modifying AggregatingScheduler to carry forward properties. In that scenario, the manifest would be set initially through sendchange, and carry forward by the Schedulers. We couldn't figure out what to do with Schedulers that have multiple upstream builders though - how do you figure out which one to copy properties from.

Comment 1

[[e-mail] (:bhearsum)]

This is going to happen with release promotion in Taskcluster!