Skip to the content ForoHackers
Log inJoin

Our production deployment procedure is a Word document

DevOps
#991 · anonymous · · Report

Not naming anyone. Just venting at two in the morning because I have to do it again.

be me deploy day open the Word document called deploy_v7_FINAL_real_USE_THIS.docx 51 steps step 14: "SSH into the server and run the script (ask Carlos if it fails)" there is no Carlos Carlos left before I joined step 31: "check that everything looks right" nobody can say what "right" looks like the screenshots are of a version of the admin page that no longer exists

I have started turning each step into a script, one per day. So far I have automated steps 1, 2 and 3. Fifty-one to go. Is this what progress feels like?

#1355 · anonymous · · Report

That is exactly what progress feels like. Keep each script runnable on its own and make step 31 a script that exits non-zero when something is wrong. "Looks right" turns into a check the first time someone writes down what right means.

#1356 · anonymous · · Report

Keep the Word document, too, as a log. Every time you automate a step, write in it "now done by script X". When it is full of those notes you can delete it with a clean conscience.

#1357 · anonymous · · Report

"ask Carlos if it fails"

Every system has a Carlos. It is a documented dependency now.

Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply