Topic

Continuous Deployment

1 post about Continuous Deployment. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Posts

Intercom
Why continuous deployment just keeps on giving - The Intercom Blog
Intercom has practiced continuous deployment since its early days, deploying code automatically after each merge to master. The pipeline uses GitHub, Codeship for the test suite, and an internal tool called Muster to push code to production EC2 instances, typically in under ten minutes. The company now deploys over 80 times a day, aiming for 100 by end of 2015, and a dashboard tracks this history over three years. This rapid feedback loop allows engineers to iterate features through internal, beta, and public stages, learning how people use the feature and how code performs in production. The automated system helps new engineers ship code on their first day and a feature in their first week by removing deployment barriers, and they demo their work at Friday sessions. Additionally, a fast and reliable deployment process discourages engineers from bypassing it during critical bug fixes, reducing risky behavior.

The best engineering reads, once a week.

Topic

1 post about Continuous Deployment. Every summary links to the original.

Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.

Newest first

Intercom
Why continuous deployment just keeps on giving - The Intercom Blog
Intercom has practiced continuous deployment since its early days, deploying code automatically after each merge to master. The pipeline uses GitHub, Codeship for the test suite, and an internal tool called Muster to push code to production EC2 instances, typically in under ten minutes. The company now deploys over 80 times a day, aiming for 100 by end of 2015, and a dashboard tracks this history over three years. This rapid feedback loop allows engineers to iterate features through internal, beta, and public stages, learning how people use the feature and how code performs in production. The automated system helps new engineers ship code on their first day and a feature in their first week by removing deployment barriers, and they demo their work at Friday sessions. Additionally, a fast and reliable deployment process discourages engineers from bypassing it during critical bug fixes, reducing risky behavior.

The best engineering reads, once a week.