Closed
Bug 1316124
Opened 8 years ago
Closed 8 years ago
[tcmigration] correctly handle the checksums in nightlies
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1305139
People
(Reporter: mtabara, Assigned: mtabara)
Details
What do we do in terms of checksums in nightly migration?
Dump from mtg notes:
[mtabara] checksums file - signingscript vs beetmoverworker
(aki) do we need this for nightly, or just releases/beta?
hang 3 jobs at end of graph: 1) gather pretty names/shas, create pretty manifest 2) sign that manifest 3) beetmove it into bucket
Postpone for now, not blocking Tier-2 not Tier-1 - skip for now from beetmover
Assignee | ||
Comment 1•8 years ago
|
||
Temporary disabled the checksums in beetmoverscript - https://github.com/mozilla-releng/beetmoverscript/commit/ef9f6498e4c7d9772480ace4c6312041d9122593
This will land along the next beetmoverscript version bump.
Assignee: nobody → mtabara
Assignee | ||
Comment 2•8 years ago
|
||
Aki fixed this for desktop nightlies.
Note to self: reminder to add them in fennec nightlies too.
Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Component: General Automation → General
You need to log in
before you can comment on or make changes to this bug.
Description
•