Two tenets of Pivotal are continuous integration and coding if you’re in front of a computer. These goals can conflict when you’ve just wrapped up a story and are about to push to a staging environment – while your final tests and deploy are running, you can’t modify your Git working tree. So you grab some coffee or check your email.buy ultram online
In the spirit of eliminating breaks enforced by devops, Dirk Kelly and Mik Freedman paired on a great way to run deploys in the background. In essence, you create a separate Git repository on your development machine, we’ll call it
deployer, that has your original Git code repository as a remote. Your deploy scripts then run in background from the deployer directory while you happily code in your original directory.
If your deployment process is anything more than a push to GitHub, this saves a good amount of time. If your project involves more than 1 pair, continuous integration and automatic deployment of all Git branches can alleviate the pain of long deploys.