Closed Bug 1500149 Opened 6 years ago Closed 6 years ago

[android-components] retire artifacts.yml in favor of settings.gradle

Categories

(Release Engineering :: Release Automation, enhancement)

Product:
Release Engineering
Component:
Release Automation
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mtabara, Assigned: mhentges)

References

Details

+++ This bug was initially created as a clone of Bug #1495829 +++ We no longer have the Massager and the jcenter bintray publishing, so we can start working on the `artifacts.yml` integration within a single-source, which ideally will be the `settings.gradle` in a for loop generative way.
More context here: Right now, the android-components graph looks like this: decision task build components beetmove components The Build task reads configurations of which components to build from here[1]. In order to expose the artifacts built by gradle as TC artifacts, the decision task uses this artifacts[2] manifest. The same artifact is used by decision task to build the definions of each of the beetmover jobs. So basically the artifacts (so-called) manifest is the source of truth for the automation side whereas the settings.gradle is the source of truth for build side. As of right now, if a new component is added (which happens ever now and then), developers need to edit both settings.gradle but also artifacts.yml. Ideally we can single-source things and get rid of `artifacts.yml` altogether. One possible solution is to infer the values from artifacts.yml in a generative way, by reading most of the information directly from settings.gradle. Since that's not really python friendly, one possible scenario is to read the gradle file from python and parse it. We can adjust what we need to in comments. Possible other better solutions are welcomed. [1]: https://github.com/mozilla-mobile/android-components/blob/master/settings.gradle [2]: https://github.com/mozilla-mobile/android-components/blob/master/automation/taskcluster/artifacts.yml
Assignee: nobody → mhentges
Done here - https://github.com/mozilla-mobile/android-components/pull/1284 First release went green with this - https://tools.taskcluster.net/groups/OvD1GGH5RiCvPj7nI7fLTQ Great job Mitchell! \o/
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Component: Release Automation: Uploading → Release Automation
You need to log in before you can comment on or make changes to this bug.