Integrate TaskCluster for release builds
Categories
(Data Platform and Tools :: Glean: SDK, defect, P1)
Tracking
(Not tracked)
People
(Reporter: janerik, Assigned: janerik)
References
Details
Attachments
(1 file)
For releasing Glean-core for Android on maven.mozilla.org we will need TaskCluster integration.
That means:
- A
.taskcluster.ymlthat decides what happens ("on github-release, create a package and upload" - A
decision_task.pythat dispatches the right tasks (build, test, package, sign, release)
We should be able to copy over most of what application-services did, change it to our needs and go with it.
I propose not running TaskCluster on every PR, CircleCI extensively covers our test suite there.
We can run it on every push to master (ensuring it's always green on TaskCluster) and then on release.
We should also document this whole process.
| Assignee | ||
Comment 1•6 years ago
|
||
Relevant links:
- https://github.com/mozilla/application-services/blob/d9a44471a727c4dbdbc801c710ade2053fd142a5/.taskcluster.yml
- https://github.com/mozilla/application-services/blob/d9a44471a727c4dbdbc801c710ade2053fd142a5/automation/taskcluster/decision_task.py
- https://github.com/mozilla/application-services/blob/master/docs/howtos/cut-a-new-release.md
- https://github.com/mozilla/application-services/blob/master/docs/build-and-publish-pipeline.md
- https://bugzilla.mozilla.org/show_bug.cgi?id=1536079
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 3•6 years ago
|
||
Yup, mostly on https://github.com/mozilla/application-services/pull/1945 getting done
| Assignee | ||
Updated•6 years ago
|
Updated•6 years ago
|
| Assignee | ||
Comment 4•6 years ago
|
||
Had another meeting with Mihai today.
Current plan:
- He's ramping up work on that app-services PR again next week
- That work will result in some documentation on what we need to do
- We will check-in end of next week about that status
- In ~2 weeks I pick up implementing our side, based on the app-service config and Mihai's input
- I also offered to review his docs as we go forward, so it's in a good shape for future users
Important: it's gonna be on us to implement the relevant parts (that is: it's going to be my task).
If all works out we should have this done in Q1.
This is only for the release part. We briefly discussed whether we can move over more of CI. I opted for putting that discussion into Q2, also depending on the outcome of the current CircleCI struggles and whether we need to move.
Comment 5•6 years ago
|
||
Sounds like a good plan!
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
Comment 6•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Updated•6 years ago
|
Description
•