Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: add note on backing up jenkins war file on upgrades #3444

Merged
merged 1 commit into from
Mar 11, 2024
Merged

doc: add note on backing up jenkins war file on upgrades #3444

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,11 +118,11 @@ to do an out-of-bound patch if a sufficientl sever issue is identified.
to identify any potential problems. Allow jenkins to upgrade itself
5. Redo step 1/2 so that any plugins that were unable to be updated due to
the older jenkins level can update themselves.
6. If necessary, and the remediation cannot be performed within the window,
identify potentially risky plugins that were held back and create an issue
to deal with them in the next cycle.

(TODO: Publish and link to video of an upgrade session)
6. If necessary, and the remediation cannot be performed within the
maintenance window, identify potentially risky plugins that were held
back and create an issue to deal with them in the next cycle.
7. Backup the main war in /usr/share/jenkins to a name with a version suffix
in case of corruption to the main jar.

### Backups

Expand Down