CI automation for tb-rust vendor
Categories
(Thunderbird :: Build Config, task)
Tracking
(thunderbird_esr115 unaffected, thunderbird123 wontfix)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr115 | --- | unaffected |
| thunderbird123 | --- | wontfix |
People
(Reporter: rjl, Assigned: rjl)
References
Details
Attachments
(3 files)
Running mach tb-rust vendor on a developer's machine is prone to odd corner case differences due to configuration differences (like .hgignores) or differences in Rust/Cargo versions.
In order to get consistent results, this process needs to be automated, and cargo vet needs to be added to the process.
This can run on Taskcluster. Ideally triggered by a push to m-c with relevant changes, but manual triggering should be available as well.
That will start a job that checks out m-c and c-c, then runs mach tb-vendor using the same Rust/Cargo version used by builds.
If changes are made, push a patch to Phab for easy landing.
| Assignee | ||
Comment 1•2 years ago
|
||
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
A bit of a hack to generate a Taskcluster hook that will trigger the tb-rust
vendor automation job. The cron task will never actually run with an empty
schedule, but with appropriate grants in ci-configuration it will be triggerable
by a CI job on mozilla-central and by Thunderbird sheriffs & releng.
Pushed by thunderbird@calypsoblue.org:
https://hg.mozilla.org/comm-central/rev/7aa19ed82835
tb-rust vendor automation. r=dandarnell
| Assignee | ||
Updated•1 year ago
|
Pushed by thunderbird@calypsoblue.org:
https://hg.mozilla.org/comm-central/rev/bd6730426190
tb-rust vendor automation. r=dandarnell
https://hg.mozilla.org/comm-central/rev/53dcb75caef4
Set up "cron" decision task to run tb-rust automation. r=dandarnell
| Assignee | ||
Comment 6•1 year ago
|
||
moz-phab submit never completes, use --yes to force it.
Description
•