Closed
Bug 679426
Opened 13 years ago
Closed 13 years ago
fix tegra dashboard for new staging server
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bear, Assigned: bear)
References
Details
(Whiteboard: [android][tegra])
Attachments
(1 file, 2 obsolete files)
49.26 KB,
patch
|
mozilla
:
review+
bear
:
checked-in+
|
Details | Diff | Splinter Review |
tegra dashboard has a real simple check for what is production/staging - that needs to be updated with the shift from bm-foopy to staging-master
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → bear
Whiteboard: [android][tegra]
Assignee | ||
Comment 1•13 years ago
|
||
change check.py so it knows what the new staging master is and also update dashboard for the new name (and also the change I made for the activity display)
Attachment #553528 -
Flags: review?(aki)
Comment 2•13 years ago
|
||
Comment on attachment 553528 [details] [diff] [review] update staging master name staging-master is going away. Also, we want to be able to run tegras in any staging master, not just one instance. Not sure what to do on the dashboard, but check.py should be at least able to look for dev or staging.
Attachment #553528 -
Flags: review?(aki) → review-
Assignee | ||
Comment 4•13 years ago
|
||
fixes tegra master and pdu for dashboard.py and check.py bug 697325 - change pdu links
Attachment #570398 -
Flags: review?(aki)
Assignee | ||
Updated•13 years ago
|
Attachment #553528 -
Attachment is obsolete: true
Comment 5•13 years ago
|
||
Comment on attachment 570398 [details] [diff] [review] combo patch for master name, tegras.json usage and pdu name change Is this running somewhere, or can I see the output somewhere?
Assignee | ||
Comment 6•13 years ago
|
||
I have it running live now (backed up the older one) - unfortunately it's the only way to truly test it
Assignee | ||
Comment 7•13 years ago
|
||
(In reply to Mike Taylor [:bear] from comment #6) > I have it running live now (backed up the older one) - unfortunately it's > the only way to truly test it tho what you may not see is the proper production/staging classification as that depends on the check.py changes to be pushed to foopies. Let me push that to foopy5 and 6 so they can test that part
Assignee | ||
Comment 8•13 years ago
|
||
tested on foopy05 and on live dashboard
Attachment #570426 -
Flags: review?(aki)
Updated•13 years ago
|
Attachment #570426 -
Flags: review?(aki) → review+
Assignee | ||
Updated•13 years ago
|
Attachment #570398 -
Attachment is obsolete: true
Attachment #570398 -
Flags: review?(aki)
Assignee | ||
Comment 9•13 years ago
|
||
Comment on attachment 570426 [details] [diff] [review] combo patch for master name, tegras.json usage and pdu name change committed changeset 1901:5b388599864f
Attachment #570426 -
Flags: checked-in+
Assignee | ||
Comment 10•13 years ago
|
||
pushed live
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•