[mach taskcluster-graph] Consider adding a try options: --no-cache (to disable caches)

RESOLVED WORKSFORME

Status

Taskcluster
Task Configuration
RESOLVED WORKSFORME
2 years ago
2 years ago

People

(Reporter: jonasfj, Unassigned)

Tracking

Details

(Reporter)

Description

2 years ago
We could probably do a hack such that --no-cache disables all cache folders.
We don't have to remove scopes, just remove task.payload.cache if it's present.

Tasks will still work, they just won't benefit from caching. The decision task
is and should obviously not be considered here.

Note: For now this would be a hack as we don't really have in-tree parameterization yet. So it would be python filtering everything.

This is intended to be used as a try flag that people set for special things,
similar to how --interactive works. Not something you enable on all tasks.

@wcosta, CC'ing as you know the in-tree stuff. I'm not sure this is useful,
just a random idea. For now maybe it's overkill, and not useful.


Note: when running with --interactive, one could easily poison caches, if one
opens a shell and starts playing around. So having the option to disable caches
could be nice. Also it's a good tool whenever we fear cache poisoning :)
(In reply to Jonas Finnemann Jensen (:jonasfj) from comment #0)
> We could probably do a hack such that --no-cache disables all cache folders.
> We don't have to remove scopes, just remove task.payload.cache if it's
> present.
> 
> Tasks will still work, they just won't benefit from caching. The decision
> task
> is and should obviously not be considered here.
> 
> Note: For now this would be a hack as we don't really have in-tree
> parameterization yet. So it would be python filtering everything.
> 
> This is intended to be used as a try flag that people set for special things,
> similar to how --interactive works. Not something you enable on all tasks.
> 
> @wcosta, CC'ing as you know the in-tree stuff. I'm not sure this is useful,
> just a random idea. For now maybe it's overkill, and not useful.
> 
> 
> Note: when running with --interactive, one could easily poison caches, if one
> opens a shell and starts playing around. So having the option to disable
> caches
> could be nice. Also it's a good tool whenever we fear cache poisoning :)

Notice we already remove caches when running on try, except for a few necessary, like tv-vcs cache.
(Reporter)

Comment 2

2 years ago
Ah, in that case it's probably not very useful...

VCS caches aren't easy to poison by accident...
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.