Loading...

XML

Word

Printable

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

is blocked by

JENKINS-50291 Customize where AsyncPeriodicWork are logged

relates to

JENKINS-50164 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running

JENKINS-49849 Automatically update when new versions of plugins and core are available

JENKINS-50294 Design (JEP) Essentials Instance Client Health Checking

links to

(1 links to)