1151605 - mozilla-taskcluster: Retrigger builds with explicit clobbering

Status: RESOLVED WONTFIX

(Taskcluster :: Services, defect)

Description

[Jonas Finnemann Jensen (:jonasfj)]

According to catlee sheriffs like to push a button and retrigger a build with
clobbering set explicitly.

We can do this by recreating the task with an ENV var indicating that cache
folders should be clobbered... So this is partly in-tree logic and partly
mozilla-taskcluster retrigger specific logic. It's another retrigger method.

Note, this would have to clobber for all subsequent builds. So this is really
not a smart way to to do it... as dirty caches remain around.

It could also be that the manual clobber request is stored in index, and that
the decision task then looks it up to see if the the builds should be clobbered.
I'm not sure... It seems wrong to me to have a timestamp outside the tree that
decides if something should clobber. But if we need that index could store it.

Comment 1

[Ryan VanderMeulen [:RyanVM]]

Does the existing API work for non-buildbot jobs? I see that clobberer.py exists within mozharness, but the logs look pretty buildbot-centric.

Comment 2

[Jonas Finnemann Jensen (:jonasfj)]

Re-evaluated if we want this, when we have bug 1151605, as purge-cache + retrigger might be a decent way to solve this.

Comment 3

[Brian Stack [:bstack]]

This could be an addition to the retrigger action task.

Comment 4

[Dustin J. Mitchell [:dustin] (he/him)]

Not needed in mozilla-taskcluster per bug 1204891, and per comment 3.