prep
- deploy neon-sftp-bridge onto new server (needs user system services)
- deploy git semaphore onto new server (may require adjustments to code?; runs as jenkins user I think; probably also user systemd service?)
access validation
- neon-sftp-bridge can access racnoss
- jenkins user can access semaphore (test by git clone via the git in the sempahore)
- jenkins user can access persistent blue systems nodes (openqa, do-builder e.g.)
jenkins prep
- adjust jenkins job updater to not generate mgmt_docker! (should be pushed to master I suppose?; simple check if user != jenkins maybe?)
- adjust paths inside jenkins to point to correct directories if necessary? (grep the xml maybe)
- shutdown jenkins and prevent it from doing aaaaaaaaaaanything. make doubly sure it doesn't switch out of this state!
- best start a script to rsync; this script should be run at least twice. once for the initial sync and then again when we are ready to roll over
- rsync entire home into jenkins data dir
- make sure to also rsync jobs.baks from the mount on drax
- copy mgmt_tooling to a temporary other name (so job numbers don't get messed up) and try to deploy tooling
- make sure all tests pass/ed
- reload jenkins configs
roll over
- put jenkins into shutdown on drax as well
- stop sftp-bridge and semaphore service on drax
- run final rsync
- fully restart jenkins on charlotte
- switch cname of domains metadata.neon.kde.org, build.neon.kde.org, download.kde.internal.neon.kde.org, images.neon.kde.org, images.neon.kde.org.uk
- ALSO update our internal DNS?
- pull jenkins out of shutdown mode on charlotte once DNS has propagated a bit
cleanup
- clean out drax' mount and jenkins home (workspaces, jobs)
- snapshot drax
- delete drax
- keep mount and snapshot for a while longer