Allow the task graph to create zips of sub-trees of the gecko tree as artifacts

RESOLVED WONTFIX

Status

Taskcluster
Task Configuration
RESOLVED WONTFIX
2 years ago
a year ago

People

(Reporter: dustin, Unassigned)

Tracking

Details

(Reporter)

Description

2 years ago
The immediate use for this is mozharness.zip, which the decision task can easily create, and which every test job needs to reference.

But we might be able to use this for tests.zip, too, or for other prerequisites for tests.

This would require a little more from the decision task than just running 'mach taskcluster-graph'
(Reporter)

Updated

2 years ago
Assignee: nobody → dustin
(Reporter)

Updated

2 years ago
Blocks: 1247703
(Reporter)

Updated

2 years ago
No longer blocks: 1247703
Depends on: 1247703
(Reporter)

Comment 1

2 years ago
Probably better (and certainly easier) to make this a separate task, especially since the tasks depending on it (tests) would also be depending on build tasks, so there's plenty of time.  Also, optimization would let us use an existing task that had already generated the cache, if necessary.
Assignee: dustin → nobody
Summary: Allow the decision task to create zips of sub-trees of the gecko tree as artifacts → Allow the task graph to create zips of sub-trees of the gecko tree as artifacts
(Reporter)

Comment 2

a year ago
I think the preference is to do a gecko checkout on testers.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.