Closed
Bug 704597
Opened 13 years ago
Closed 13 years ago
populate new foopys with required tools
Categories
(Release Engineering :: General, defect, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bear, Assigned: hwine)
References
Details
(Whiteboard: [android][tegra][buildduty])
Attachments
(3 files)
11.28 KB,
patch
|
bear
:
review+
bear
:
checked-in+
|
Details | Diff | Splinter Review |
4.03 KB,
patch
|
bear
:
review+
bear
:
checked-in+
|
Details | Diff | Splinter Review |
3.92 KB,
patch
|
bear
:
review+
|
Details | Diff | Splinter Review |
once the 6 new foopys are up, populate them with tools and start assigning tegras todo list: 1. update tegras.json for cdu and tegra assignment 2. update foopies.sh for tegra assignment 3. profit!
Reporter | ||
Updated•13 years ago
|
Comment 1•13 years ago
|
||
If you want to start in, the following are up and ready to roll: foopy18 foopy19 foopy20 foopy22 foopy23 I expect foopy20 will need to go down at some point, as its partner foopy21 needs to be swapped out with foopy24, so coordinate with Jake.
Reporter | ||
Updated•13 years ago
|
Assignee: bear → nobody
Whiteboard: [android][tegra] → [android][tegra][buildduty]
Assignee | ||
Comment 2•13 years ago
|
||
New hardware is newest model, which requires Lion. First install will need to be crosschecked that it still works-as-desired. (installation instructions no longer accurate.) Currently working on foopy18
Assignee: nobody → hwine
Priority: -- → P3
Assignee | ||
Updated•13 years ago
|
Status: NEW → ASSIGNED
Comment 3•13 years ago
|
||
foopy20 is good to go, and foopy24 is up now. foopy21 is going to desktop for repairs.
Assignee | ||
Comment 4•13 years ago
|
||
foopy18 has base software installed & tested (first Lion install). Doc updated <https://wiki.mozilla.org/index.php?title=ReferencePlatforms/Test/Foopy> - now see if it's repeatable. Starting on foopy19
Assignee | ||
Comment 5•13 years ago
|
||
Attachment #582113 -
Flags: review?(bear)
Reporter | ||
Updated•13 years ago
|
Attachment #582113 -
Flags: review?(bear) → review+
Assignee | ||
Comment 6•13 years ago
|
||
Rest of foopies are provisioned: foopy19, foopy20, foopy22, foopy23, foopy24. tegras have been configured for the foopies, and added to the staging master, per normal practice, and are processing jobs. After a successful overnight bakein, they can be moved to the production master.
Assignee | ||
Comment 7•13 years ago
|
||
Contains a number of messages to help newbies, and the new tegra data (already used to configure new foopies)
Attachment #582196 -
Flags: review?(bear)
Assignee | ||
Comment 8•13 years ago
|
||
automate tedious (hence error prone) data transcription from IT spreadsheet. Very much an ugly hack, constants need to be manually edited for each batch of new tegras & foopies.
Attachment #582197 -
Flags: review?(bear)
Reporter | ||
Updated•13 years ago
|
Attachment #582196 -
Flags: review?(bear) → review+
Reporter | ||
Comment 9•13 years ago
|
||
Comment on attachment 582197 [details] [diff] [review] helper script to generate json & shell data I'm not sure if I want foopies.sh updated from the inventory spreadsheet just yet, but maybe I just need convincing :) will ask some questions tomorrow and finish the review
Assignee | ||
Updated•13 years ago
|
Attachment #582113 -
Flags: checked-in?
Assignee | ||
Updated•13 years ago
|
Attachment #582196 -
Flags: checked-in?
Reporter | ||
Comment 10•13 years ago
|
||
Comment on attachment 582113 [details] [diff] [review] add 80 new tegras to tegras.json committed changeset 2054:03552fe0d46c
Attachment #582113 -
Flags: checked-in? → checked-in+
Reporter | ||
Comment 11•13 years ago
|
||
Comment on attachment 582196 [details] [diff] [review] enhanced error handling & messages for newbies committed changeset 2055:545bd962188f
Attachment #582196 -
Flags: checked-in? → checked-in+
Reporter | ||
Updated•13 years ago
|
Attachment #582197 -
Flags: review?(bear) → review+
Reporter | ||
Updated•13 years ago
|
Status: ASSIGNED → 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
•