Taskgraph - supply schema for "Parameters"
Categories
(Release Engineering :: General, enhancement)
Tracking
(firefox69 fixed)
| Tracking | Status | |
|---|---|---|
| firefox69 | --- | fixed |
People
(Reporter: mhentges, Assigned: mhentges)
References
Details
Attachments
(1 file)
As part of adding git support for taskgraph, we can no longer uniformly define all taskgraph "parameters" as required (for example, pushlog_id isn't relevant for git clones).
This will leverage taskgraph's schema tooling to validate parameters and allow conditionally required values.
| Assignee | ||
Comment 1•6 years ago
|
||
Tom, would you recommend making this change to the extracted taskgraph, then porting it to in-tree, or the other way around?
Comment 2•6 years ago
|
||
My general workflow has to get the version targeted at mozilla-central reviewed and landed first, and then land on ci/taskgraph. At the moment, the mozilla-central copy is critical code, and ci/taskgraph less so, so the review there is more critical, and there are more stakeholders.
For development, I've sometime worked on ci/taskgraph first, but ported to mozilla-central for review, before porting back to ci/taskgraph to land.
| Assignee | ||
Comment 3•6 years ago
|
||
I've tested this with ./mach python-test taskcluster, as well as playing with ./mach taskgraph tasks.
I'm very open to recommendations for further testing or workflow :)
Updated•6 years ago
|
Updated•6 years ago
|
Comment 5•6 years ago
|
||
Backed out 2 changesets (Bug 1535056, Bug 1513854) for linux build bustages and failed Gecko Decision Task CLOSED TREE
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=244115091&repo=autoland&lineNumber=59
| Assignee | ||
Comment 7•6 years ago
•
|
||
I had left my patch sitting and it got stale - I should've re-tested it before landing.
I'll re-test and re-land this ticket later (next week, hopefully)
| Assignee | ||
Comment 8•6 years ago
|
||
The failure was caused by pushlog_id being a basestring, not unicode
Updated•6 years ago
|
Comment 10•6 years ago
|
||
| bugherder | ||
Comment 11•6 years ago
|
||
Backed out changeset 48687a76aec5 for causing nightly builds to fail.
Backout link: https://hg.mozilla.org/mozilla-central/rev/5cc220ddf028de011a922042ee9ba691b94d055d
Push with failures: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&resultStatus=testfailed%2Cbusted%2Cexception&revision=900ff508219cddc29c6f6307c65f0e90c3422c24&selectedJob=248684134
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=248684134&repo=mozilla-central&lineNumber=79
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 12•6 years ago
|
||
Ahh, I tested with taskgraph decision, but I was using an old head-ref that didn't contain recent payload changes.
I'll update, learn how to run against try, and land again
| Assignee | ||
Comment 13•6 years ago
|
||
Associated try has passed the decision task
Comment 14•6 years ago
|
||
Comment 15•6 years ago
|
||
| bugherder | ||
Comment 16•6 years ago
|
||
Backed out changeset 50beca34e939 (Bug 1535056) for causing cron tasks bustages a=backout
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=248921207&repo=mozilla-central&lineNumber=48
Backout: https://hg.mozilla.org/mozilla-central/rev/8d86cc081fe5d16980a0a610af6b967cc03bf814
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 17•6 years ago
|
||
I've resolved the specific error (--optimize-target-tasks was being parsed to an int, not a bool).
I'll land again (after checking with Tom that my solution is OK), and I'll continue to iterate if it fails
Updated•6 years ago
|
Comment 18•6 years ago
|
||
Comment 19•6 years ago
|
||
| bugherder | ||
Description
•