1490961 - [declarative artifacts] enrich the beetmover transforms to encompass the artifactMap information for Fennec nightlies

Status: RESOLVED FIXED

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

Description

[Mihai Tabara [:mtabara]⌚️GMT]

So far in our logic, the manifest in-tree contains all the information for all artifacts. Our target in this bug is to the artifactMap dictionary, encompassing information about the files to be sent. 

Rather than trying to add all of them at once, I think it's best to focus on the simplest of them (such as simple `beetmover` transforms which are used by Fennec jobs). Then we can iterate with the `beetmover-repackage` and so on.



Therefore, to sum-up the TODOs:
* this is blocked by landing the manifest in-tree, tracked in bug TODO.
* once the manifest is in tree, choose one transform from one of the beetmover jobs and enrich the manifest with the artifactMap dictionary. More information on how this is supposed to look like is here[1], in Lisa's PR unit tests. Can add more information again here if we need to.
* once the new payload is in place, new staging releases and beetmoverscript changes pinned to a puppet environment, should handle that particular beetmover job without the existing templates. The beetmoverscript changes are tracked in bug TODO and need to be landed first. 

[1]: TODO

Comment 1

[Mihai Tabara [:mtabara]⌚️GMT]

The above TODO refers to bug 1490959.

Comment 2

[Mihai Tabara [:mtabara]⌚️GMT]

Simon did a great work wrapping this up. The groundwork just landed in inbound[1] and is following the normal tree process of riding the trains.

We'll make the necessary amendments on the fly.

[1]: https://hg.mozilla.org/integration/mozilla-inbound/rev/e375e10f670a