The way that artifact-prefix works is that it applies to the consuming task's fetches... meaning that changing the prefix requires working out the new paths for every fetch in the consuming task. This ticket tracks allowing to "opt-out" of the artifact prefix mechanism for individual fetches.

aki: is my understanding above correct? Is this how artifact-prefix is intended to work? It would be much more useful if artifact-prefix meant things for producer tasks, and was gracefully interpolated into the consuming task fetches automatically. But that's not what we have, IIUC.

artifact-prefix could, and likely should, mean something for producer tasks, if and when we tie declarative artifacts in everywhere. (Right now declarative artifacts list things for consumer tasks to use, but aiui can't change the outputs of, say, a build task.)

I think your statement is accurate. If you're changing things for release tasks (e.g. shippable), you need to make sure your changes are reflected in declarative artifacts and matches artifact-prefix, or downstream release tasks will break. If this is just for testing, we don't have to worry about that.

The way that artifact-prefix works is that it applies to the
consuming task's fetches... meaning that changing the prefix
requires working out the new paths for every fetch in the consuming
task. This allows to "opt-out" of the artifact prefix mechanism for
individual fetches.

Depends on D43534

Backed out changeset 4a7e698d5033 (bug 1576707) for linting failure on /job/init.py:242:33.

Backout: https://hg.mozilla.org/integration/autoland/rev/97d70de52aec45bde0ce4f3d7e6001c979730d63

Push that started the failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&resultStatus=pending%2Crunning%2Csuccess%2Ctestfailed%2Cbusted%2Cexception&revision=4a7e698d5033d9703aa7e91d68ffe793d55a5a08&selectedJob=263737237

Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=263737237&repo=autoland&lineNumber=223

https://hg.mozilla.org/mozilla-central/rev/b9dbcc4fdabf

Clearing NI since I relanded this.

https://hg.mozilla.org/mozilla-central/rev/422c28fdc436
https://hg.mozilla.org/mozilla-central/rev/51ea1470a436
https://hg.mozilla.org/mozilla-central/rev/282e733216aa
https://hg.mozilla.org/mozilla-central/rev/ce148e5333aa

You landed a typo here:
https://hg.mozilla.org/mozilla-central/rev/ce148e5333aa6b7f5376c22c6d9727a4639b93fe#l5.93
if len(dep_dep_tasks) == 0

Fixing the typo, we see this in TB:
Exception: addon-calendar-l10n can't fetch toolchain-linux64-libdmg artifacts because there are no tasks with label toolchain-linux64-libdmg in kind dependencies!

That's more helpful.

https://hg.mozilla.org/mozilla-central/rev/6333ec1b48dd

Backports https://phabricator.services.mozilla.com/D49775 to taskgraph

Depends on D69341

Backports https://phabricator.services.mozilla.com/D49776 to taskgraph

Depends on D69342

Backports https://phabricator.services.mozilla.com/D49777 to taskgraph

Depends on D69343

Backports https://phabricator.services.mozilla.com/D49699 to taskgraph

Depends on D69344

Backports https://phabricator.services.mozilla.com/D50043 to taskgraph

Depends on D69345