Closed Bug 596831 Opened 14 years ago Closed 8 years ago

Allow non-RelEng folk to enable/disable snippets and move/copy them between channels

Categories

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

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: christian, Unassigned)

References

Details

(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2086] [release-process-improvement][automation])

Allow non-RelEng folk to enable/disable snippets and move/copy them between channels.

During release the snippets (what's live and where) are a huge black box. It would be nice for me to not have to bug RelEng for the simple case of viewing snippet status and the typical betattest -> beta -> releasetest -> release push dance.

A web UI ontop of snippet management would do nicely.

This could be one step away from automation that moves them for me based on other systems.
Whiteboard: [release-process-improvement]
Don't disagree that this would be nice, but we don't even have this for releng yet (bug 594930).
Depends on: 594930
Priority: -- → P5
Whiteboard: [release-process-improvement] → [release-process-improvement][automation]
(In reply to comment #0)
> During release the snippets (what's live and where) are a huge black box. It
> would be nice for me to not have to bug RelEng for the simple case of viewing
> snippet status and the typical betattest -> beta -> releasetest -> release push
> dance.

Viewing snippet status seems low-risk (could be totally read-only) and could probably be done relatively soon. If that is useful, it might make sense to explicitly tackle that first. Christian what do you think?
A simple tool to report on where snippets are pointing would be a big help here, instead of poking around at individual files.
Yes, just a viewing tool would be super useful. The ability to shuffle them around on channels is an added bonus :-)
I intend to make this possible with the initial admin interface of Balrog.
Depends on: balrog
Product: mozilla.org → Release Engineering
The UI allows for this now, the rest is just policy/training. Alex, Lukas - I'd love to get you (and Bhavana/Preeti if appropriate) to play around with the dev interface a bit to get comfortable with it whenever you're ready. Once you get access you'll be able to do Aurora disabling/enabling on your own!
Assignee: nobody → bhearsum
bug 933944 describes a race condition that can make bad things happen. I'd like to fix that before we do this...
Depends on: 933944
Massimo is working on improving the rules page to be much more user friendly. I think we should wait for that before doing this too.
Depends on: 929555
I'm unassigning this from myself because it's going to be awhile. We need Balrog in production for betas/releases first, and we probably want to make specific actions available via ship it, which depends on bug 886522
Assignee: bhearsum → nobody
Depends on: 886522
Component: Other → Release Automation
QA Contact: bhearsum
Whiteboard: [release-process-improvement][automation] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2077] [release-process-improvement][automation]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2077] [release-process-improvement][automation] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/2086] [release-process-improvement][automation]
I believe this is doable in Balrog now.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.