Stop publishing the Snap to the Snap store
Categories
(Release Engineering :: Release Automation: Snap, task)
Tracking
(Not tracked)
People
(Reporter: mkaply, Assigned: mozilla)
Details
(Keywords: leave-open)
Attachments
(7 files)
63 bytes,
text/x-github-pull-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
63 bytes,
text/x-github-pull-request
|
Details | Review | |
56 bytes,
text/x-github-pull-request
|
Details | Review | |
63 bytes,
text/x-github-pull-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
55 bytes,
text/x-github-pull-request
|
Details | Review |
With the transition of the Snap, we need to stop the final step of publishing to the store.
We should keep all the other work.
Per discussions, this was going to happen for 92.
Unfortunately I forgot to file this bug earlier.
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Comment 2•3 years ago
|
||
This is a full "don't push to the store at all", so we will need to
- disable the ability of the pushsnap pool to push to the store pre-92.0 push Tuesday - that's the PR above, to roll out once I get the tests green
- delete the release-{,secondary-}snap-push kinds and any transforms etc specific to those kinds
- uplift patch from 2 to release trains (do we do esr?)
- delete pushsnapscript from scriptworker-scripts, delete pools (k8s-autoscale, taskcluster-cloudops, k8s-sops)
Assignee | ||
Comment 3•3 years ago
|
||
Assignee | ||
Comment 4•3 years ago
|
||
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 5•3 years ago
|
||
Assignee | ||
Comment 6•3 years ago
•
|
||
1 is done. 2 is the gecko patch above, which we'll uplift for step 3.
I have 2 of the four delete pushsnapscript patches attached. 3/4 is here; 4/4 is removing the secrets in the k8s sops repo.
Assignee | ||
Comment 7•3 years ago
|
||
(2) is scheduled to Lando.
I'll leave steps 3 and 4 for next week, after the long weekend. Because (1) landed already, the pushsnap task for 92 should be noop.
Pushed by asasaki@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0f0309f1f8b6 remove pushsnap tasks. r=releng-reviewers,bhearsum DONTBUILD
Assignee | ||
Comment 9•3 years ago
|
||
Ben is suggesting we leave steps 3 and 4 for a cycle or two, until we know the distro builds are stable.
That sounds like it could be a good idea, especially if backing out the removal is non-trivial.
Comment 10•3 years ago
|
||
bugherder |
Assignee | ||
Comment 11•3 years ago
|
||
Assignee | ||
Comment 12•3 years ago
|
||
https://hg.mozilla.org/releases/mozilla-release/rev/bfc96f4a3e02dcfad906c46f03ab8aa95253ce52
https://hg.mozilla.org/releases/mozilla-esr91/rev/45bc8d1f4315b5380728ee2265c5abe036e851d5
We got mozilla-beta for free on merge-day yesterday. So unless we do a 92 dot build off a relbranch, we should be clear of pushsnap tasks on all release trains except esr78. I'll reenable the push in the pushsnap pool, then rerun the esr78 pushsnap task.
Assignee | ||
Comment 13•3 years ago
•
|
||
Current status:
- I was not able to use the
retrigger (decision)
action, because of scopes. Perhaps if I went through the TC UI instead of Treeherder? But: - I was able to craft a relpro :snowman: graph with just the push snap task on esr78. We should get this task for free for the last esr78 release next month.
- Once esr78 is EOLed, we can proceed removing the pushsnap pool entirely, but until then let's leave this bug open.
Assignee | ||
Comment 14•3 years ago
|
||
Assignee | ||
Comment 15•3 years ago
|
||
Comment 16•3 years ago
|
||
Pushed by asasaki@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/f992905fe25d remove pushsnap scopes. r=releng-reviewers,jcristau
Assignee | ||
Comment 17•3 years ago
|
||
I also removed the secrets from our k8s sops repo.
Assignee | ||
Updated•3 years ago
|
Description
•