Closed
Bug 1088204
Opened 10 years ago
Closed 8 years ago
Display a notification banner in the treeherder UI when a production push occurs
Categories
(Tree Management :: Treeherder, defect, P5)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jfrench, Assigned: KWierso)
References
()
Details
Attachments
(1 file)
Just an idea discussed today, it might be handy if during a push to production, we:
- push an IRC gitbot-like message to the #treeherder channel
- potentially also provide in-app messaging that a push is underway
For the 2nd part, if we did that, perhaps a Treeherder balloon dialogue overlaying the top navbar, and message perhaps similar to:
"The production instance is being re-deployed, please grab a coffee for [n]minutes, then reload this page." - with an accompanying dismiss button.
This would prevent Sheriffs and other users from thinking Treeherder has gone down, and differentiating between that and a prod push.
Comment 1•10 years ago
|
||
(In reply to Jonathan French (:jfrench) from comment #0)
> - push an IRC gitbot-like message to the #treeherder channel
This is bug 1076885 :-)
Let's make the bug about this second part (which will likely be lower priority once bug 1076885 is fixed and/or we sort out the rough edges in our deployment script):
> - potentially also provide in-app messaging that a push is underway
Blocks: 1080757
Summary: Provide messaging to the channel (and/or in app) when a production push occurs → Display a notification in the treeherder UI when a production push occurs
Updated•10 years ago
|
Summary: Display a notification in the treeherder UI when a production push occurs → Display a notification banner in the treeherder UI when a production push occurs
Reporter | ||
Comment 2•10 years ago
|
||
Gah, thanks Ed. :) Perhaps Bugzilla didn't warn me of a possible dupe since 1076885 was a different product.
Comment 3•10 years ago
|
||
Yeah unfortunately the configs for Chief are centralised and not under our control, so I filed over there.
Updated•10 years ago
|
Priority: P4 → P5
Comment 4•8 years ago
|
||
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → wkocher
Assignee | ||
Comment 5•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
This appears to work for me when testing locally with vagrant (plus manually creating the revision.txt file since I don't think it gets created normally in a vagrant run).
It does add a dependency on gitpython, which we might not want to have running on the server, so I'm open to better ideas on how to get the server's revision. :)
Attachment #8798540 -
Flags: feedback?(emorley)
Updated•8 years ago
|
Attachment #8798540 -
Flags: feedback?(emorley) → feedback+
Assignee | ||
Updated•8 years ago
|
Attachment #8798540 -
Flags: review?(emorley)
Comment 6•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
UI-only solutoj now, so punting to Will :-)
Attachment #8798540 -
Flags: review?(emorley) → review?(wlachance)
Comment 7•8 years ago
|
||
Solution, even
Comment 8•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
This lgtm, I have a few comments and a suggestion on how to implement the notification as an infobox.
Attachment #8798540 -
Flags: review?(wlachance) → review+
Assignee | ||
Comment 9•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
Re-flagging review because the patch has made a bunch of changes since the r+.
Attachment #8798540 -
Flags: review+ → review?(wlachance)
Comment 10•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
Seems like a good approach, but there's a few changes I'd like to see before this goes in.
Attachment #8798540 -
Flags: review?(wlachance) → review-
Assignee | ||
Comment 11•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
Addressed all but one of the comments, and the fifth doesn't seem super important to me.
Attachment #8798540 -
Flags: review- → review?(wlachance)
Comment 12•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
Just a few more things to be addressed. Sorry for the delay reviewing this, will be faster next time. :)
Attachment #8798540 -
Flags: review?(wlachance)
Assignee | ||
Comment 13•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
How about this?
Attachment #8798540 -
Flags: review?(wlachance)
Comment 14•8 years ago
|
||
Comment on attachment 8798540 [details] [review]
[treeherder] KWierso:bug1088204 > mozilla:master
This is very close, but I think it would be better if you created a partial especially for the update and included it from index.html, so it was always visible no matter what the user's scroll position. r+ with the addressed.
Attachment #8798540 -
Flags: review?(wlachance) → review+
Comment 15•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/b6f411d8cd9fc0279f9248f6a788b77b7081d1e5
Bug 1088204 - Warn the user when server revision has changed (#1901) r=wlach
Assignee | ||
Updated•8 years ago
|
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.
Description
•