3 ms·

Note to OP - when that developer leaves the company they will host a session called a "handover". At the handover meeting they rapidly run through how they thin

Note to OP - when that developer leaves the company they will host a session called a "handover". At the handover meeting they rapidly run through how they think the pipeline works, lay out some caveats and then they're gone. That's the documentation. You own the pipeline now. It's probably a good idea to take vacation whenever the person who owns the Jenkins pipeline announces that they've handed in their notice. Otherwise you might be invited to the handover meeting.

jacurtis 4y ago
Yep, been to a lot of these. We call them "KT" sessions (knowledge-transfer). I shiver all down my spine when I hear "KT". You basically take the person who's been working on something for thousands of hours most likely and has probably written a lot of work arounds and shortcuts to get their job done and they now have a 1 hour zoom session to brain dump their entire existance onto the poor souls who have to pick up the pieces when they are gone. After that hour, they basically sign off with: glhf