The deployment production line

@article{Humble2006TheDP,
  title={The deployment production line},
  author={Jez Humble and Chris Read and Dan North},
  journal={AGILE 2006 (AGILE'06)},
  year={2006},
  pages={6 pp.-118}
}
Testing and deployment can be a difficult and time-consuming process in complex environments comprising application servers, messaging infrastructure and interfaces to external systems. We have seen deployments take several days, even in cases where teams have used automated builds to ensure their code is fully tested. In this paper we describe principles and practices which allow new environments to be created, configured and deployed to at the click of a button. We show how to fully automate… 

Figures from this paper

Defining metrics for continuous delivery and deployment pipeline

This paper addresses metrics that are suited for supporting continuous delivery and deployment through a descriptive and exploratory single case study on a project of a mid-sized Finnish software company, Solita Plc.

One size does not fit all: an empirical study of containerized continuous deployment workflows

A mixed-methods study to shed light on developers' experiences and expectations with containerized CD workflows and finds two prominent workflows, based on the automated builds feature on Docker Hub or continuous integration services, with different trade-offs.

Automated build service to facilitate Continuous Delivery

A service that supports continuous delivery by providing automated building, testing, signing and deployment of software that runs in production environment at IKEA IT and provides a high level of automation.

Making "Push On Green" a Reality

Making rollouts as easy and as automated as possible is described, so that when a “green” condition is detected, the authors can more quickly perform a new rollout.

TOWARD CONTINUOUS DELIVERY OF A NONTRIVIAL DISTRIBUTED SOFTWARE SYSTEM

By implementing patterns such as deployment pipelines* and immutable release candidates the authors hope to simplify the release process and demonstrate increased throughput of changes, quality and stability in the future.

Continuous Deployment at Facebook and OANDA

It is shown that continuous deployment does not inhibit productivity or quality even in the face of substantial engineering team and code size growth, the first study to show it is possible to scale the size of an engineering team by 20X and thesize of the code base by 50X without negatively impacting developer productivity or software quality.

Simplifying Release Engineering for Multi-Stacked Container-Based Services

This thesis aims to explore the possibilities of simplifying release engineering processes, with the usage of multi-stacked container-based services, by designing and implementing a model that enables the documentation, configuration and orchestration of the deployed services, that are deployed with theusage of Docker containers.

Automated system for deployment of websites and windows services to the production servers

An automatic system for deployment of websites and windows services to the production servers is developed and implemented using windows sql server as a database, asp.net as the front end technology and c# the used programming language.

Towards Continuous Delivery in System Integration Projects Introducing a Strategy to Achieve Continuous Delivery and Test Automation with FitNesse

This thesis presents a strategy to introduce continuous delivery and test automation with FitNesse in system integration projects. It was designed for Everett's identity solutions projects, but is

Synthesizing Continuous Deployment Practices Used in Software Development

It is observed that continuous deployment necessitates the consistent use of sound software engineering practices such as automated testing, automated deployment, and code review, which are used by software companies.