Closed
Bug 1701359
Opened 3 years ago
Closed 3 years ago
Create staging scopes and workflow for EngWF Sentry release task
Categories
(Release Engineering :: General, task)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mhentges, Assigned: mozilla)
References
Details
Attachments
(1 file)
As discussed with Aki over Zoom today:
I'd like to have a task that informs Sentry of each revision in mozilla-central
as they're pushed. Unfortunately, my implementation is failing, and it's unclear what the fix is without further debugging.
It would be helpful to have:
- Multiple levels of the secret for this task: at least one for
try
, and one for production (mozilla-central
). - Access for my team (myself, sheehan@mozilla.com, glob@mozilla.com) to get and set these secrets.
- Scopes for
try
workers to see the level 1 secret, Scope formozilla-central
workers to see the level 3 secret.
I think that will provide the flexibility that will help me narrow down why my task is failing :)
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → aki
Status: NEW → ASSIGNED
Pushed by asasaki@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/5c23f21897d9 grant engworkflow team access to engwf secrets r=releng-reviewers,mtabara
Assignee | ||
Comment 3•3 years ago
|
||
Ok, Mitch, you should be set with scopes to set and get secrets, and test with the level 1 secret on Try.
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•3 years ago
|
||
Thanks Aki, that's great! 💃🐧
You need to log in
before you can comment on or make changes to this bug.
Description
•