Yep, clearly shows the value of a properly configured CI/CD pipeline.

ransom1538 · on March 10, 2018

Yeah here it is:

git pull; sh tests; rsync /prod/ all@prod:/var/www/

^ That is copyrighted by the way. Ill take a consultant fee. I know - I know it should be thousands of lines of puppet, jenkins, hooks, Kubernetes, Salt, and 2 million lines of python and ELM all piped through Docker containers -- I am NOT an animal.

xevb3k · on March 10, 2018

Enterprise edition with test validiation and continuous deployment:

while true; do git pull; sh tests && rsync /prod/ all@prod:/var/www/;done

hedora · on March 11, 2018

You forgot to rewrite the logic in xml, and then fetch it over the internet from unknown third parties by tunneling it through json, then http. Bonus points if the the whole thing is deployed via docker hub.

pronoiac · on March 10, 2018

!!!

those ... those semicolons should be &&

hedora · on March 11, 2018

You need to invoke the script via ‘sh -ex’ for proper exception handling + debuggability.

Also, mktemp and shell exit traps are your friends.

paulddraper · on March 11, 2018

Except that this is Facebook, so `sh tests` is going to take 900 cpu-hours

davedx · on March 10, 2018

Git pull - you have a staging server!?