Closed
Bug 827903
Opened 13 years ago
Closed 12 years ago
Avoid the need to stop/start the foopies to deploy a newer SUT agent
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: armenzg, Unassigned)
Details
verify.py has the ability to update the SUT agent if specified.
IIRC it would cause the job to look red.
Perhaps we can decouple the need to update the sut agent on the first run of verify.py and have a second run of verify.py at the end of the job which only updates the sut agent.
I'm speaking from memory so I can be wrong.
I can help with this if this is wanted.
Comment 1•12 years ago
|
||
Not sure if this is still an issue since clientproxy is gone. I updated all the foopies this morning and the steps I used were
graceful all mobile masters
update foopies
start masters
It took less than an hour.
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Comment 2•12 years ago
|
||
This is even easier now since at-end-of-job the slaves disco from buildbot then run verify.py (which does the SUT update) then starts buildbot again!
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•7 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•