News Stay informed about the latest enterprise technology news and product updates.

Ancestry.com's top lessons learned from continuous software development

6/8

Increase throughput and keep your production pipeline robust

Source:  Nastco/Thinkstock

The primary goal of a Continuous Delivery pipeline is to increase throughput with simultaneous execution of stages, followed by early fault detection using highly automated testing. Longer delays between check-ins and releases can result from an increase in the number of quality gates, exact repetition of tests in differing quality gates, or longer sequential tests. These factors impact the time-to-resolve when a quick fix is needed.

If management expects quicker turnaround for last-minute software patches, this is inconsistent with the concept of a Continuous Delivery model. Continuous Delivery is an automated build, deploy, test, and release process -- not a means to last-minute development. Quality is important. What goes to production must be robust. Similar to a factory assembly line, a production pipeline increases throughput. It does not decrease cycle times.

View All Photo Stories

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

-ADS BY GOOGLE

SearchMicroservices

TheServerSide.com

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchHRSoftware

SearchHealthIT

DevOpsAgenda

Close