-
Story
-
Resolution: Fixed
-
Minor
-
-
Evergreen - Milestone 1
For Milestone 1, we need to implement the fact the evergreen-client upgrades Jenkins.
From a high level, this should be done as follows:
- The client is instructed to perform an upgrade (Not sure: I think this is
JENKINS-50848) - It downloads what needs to be (plugins, new war) and puts them at the expected place for next startup (see below)
- Restart Jenkins to pick-up update
- Health-check it, see JEP-304
- If unhealthy, roll it back to previous, see JEP-302
Open questions
- What if the current state, i.e. even before upgrading, is unhealthy already?
- "expected place for next startup": we should probably define some location on the disk for caching those things, for instance to be able to revert in case we need to rollback without downloading things again, etc.
- is blocked by
-
JENKINS-51272 Restore pusher service as a socket.io service with basic ping command support
-
- Resolved
-
[JENKINS-50958] Implement the Jenkins upgrade by the evergreen-client
| Epic Link |
New:
|
| Rank | New: Ranked lower |
| Rank | New: Ranked higher |
| Link |
New:
This issue is blocked by |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
| Labels | Original: essentials | New: essentials evergreen |
| Labels | Original: essentials evergreen | New: evergreen |