-
Task
-
Resolution: Fixed
-
Minor
-
-
Evergreen - Milestone 1
I need to explore the idea suggested by sag47 of using a Git repository on-disk for checking in .xml.files before we run an upgrade process.
In addition the approach should rollback if there is a failure, such as Jenkins failing to come up properly.
- blocks
-
JENKINS-50320 Adjust JEP 301 once snapshotting data JEP is accepted
-
- Closed
-
- is blocked by
-
JENKINS-50291 Customize where AsyncPeriodicWork are logged
-
- Resolved
-
- relates to
-
JENKINS-50164 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
-
- Closed
-
-
JENKINS-49849 Automatically update when new versions of plugins and core are available
-
- Resolved
-
-
JENKINS-50294 Design (JEP) Essentials Instance Client Health Checking
-
- Resolved
-
- links to
We had a chat today with rarabaolaza and he vented a quite important thing we might want to do IMO: to reduce the risk of creating more things than necessary when Jenkins starts again after an upgrade, puting it in quiet start mode could help.
Only once the evergreen client has performed the upgrade, and checked Jenkins is judged healthy, would it automatically cancel its quiet mode.