Closed Bug 1413153 Opened 7 years ago Closed 7 years ago

investigate if we still need the beetmover image task for Firefox in-tree

Categories

(Release Engineering :: Release Automation: Other, enhancement)

Product:
Release Engineering
Component:
Release Automation: Other
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: mtabara, Assigned: mtabara)

References

Details

Most likely this is a no-op. We no longer need Docker images if we switch to beetmoverworkers. This bug can track the cleanup of docker images though. Otherwise, a free no-op to start a future morning with :)
We no longer need this. Once firefox beetmover tasks are in-tree (currently WIP) we will no longer use any Docker image because we won't be needing mozharness script (old beetmover https://hg.mozilla.org/mozilla-central/file/tip/testing/mozharness/scripts/release/beet_mover.py) but instead the beetmover scriptworkers will do the job.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.