Details
-
Epic
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Won't Do
-
Evergreen Automatic Rollback System
-
-
Evergreen - Milestone 1, Evergreen - Milestone 2
Description
The automated rollback system has been designed, but not implemented yet.
Related JEPs/documents:
Acceptance criteria
- Set up an evergreen instance, it is at UL-X
- publish a (broken) update level (example: adding a plugin without a required dependency) => instance upgrades to UL-X
- after restart, evergreen client detects Jenkins cannot restart, and rolls back to UL-X.
- Jenkins is accessible again
- a correct UL is published, Jenkins can upgrade to it
Attachments
Issue Links
- blocks
-
JENKINS-53324 Author a jenkins.io blog post announcing Milestone 1
-
- Resolved
-
- depends on
-
JENKINS-53983 Per-instance tainting still serves the tainted level if you're "coming from" a lower level
-
- Resolved
-
-
JENKINS-53964 Drop uuid_checksum_uniq unique key constraint
-
- Closed
-
-
JENKINS-53499 Improve tests to avoid race condition for updates during startup
-
- Closed
-
- is blocking
-
JENKINS-53419 Demo Jenkins Evergreen successfully at DevOps World Jenkins World in SF
-
- Resolved
-
Started trying to find some library to manage a git repo. Until now, no luck: