The highways and country roads to continuous deployment

@article{Leppnen2015TheHA,
  title={The highways and country roads to continuous deployment},
  author={Marko Lepp{\"a}nen and Simo M{\"a}kinen and Max Pagels and Veli-Pekka Eloranta and Juha Itkonen and Mika M{\"a}ntyl{\"a} and Tomi M{\"a}nnist{\"o}},
  journal={IEEE Software},
  year={2015},
  volume={32},
  pages={64-72}
}
As part of a Finnish research program, researchers interviewed 15 information and communications technology companies to determine the extent to which the companies adopted continuous deployment. They also aimed to find out why continuous deployment is considered beneficial and what the obstacles are to its full adoption. The benefits mentioned the most often were the ability to get faster feedback, the ability to deploy more often to keep customers satisfied, and improved quality and… 

Tables from this paper

Controlled Continuous Deployment: A Case Study From The Telecommunications Domain

This paper proposes a Controlled Continuous Deployment (CCD) approach, which considers the constraints software-intensive embedded systems have, such as high reliability and availability requirements, limited possibility for rollback after deployment, and the high volume of in-service systems in the market.

Perceived benefits of Continuous Deployment in Software-Intensive Embedded Systems

The objective of this paper is to identify perceived benefits after transitioning to continuous deployment from a long-cycle release and deployment process at a multinational telecommunication company focusing on large and complex embedded software.

Framework for orchestrating application deployments using multiple deployment technologies

This thesis provides a framework that enables and manages the deployment with multiple deployment technologies by first defining a technology agnostic model on the basis of the Essential Deployment Meta Model and then the automatic execution with the desired tools.

Problems and Solutions of Continuous Deployment: A Systematic Review

This paper is a systematic literature review of the problems and the solutions found when implementing the continuous deployment practice inside an organization and presents which solution can be applied to which problem.

Continuous Integration, Deployment and Delivery Automation in AWS Cloud Infrastructure

The analysis shows that the proposed pipeline providing a productive environment for the developing team to automate the build and deploy their code up to the production line and the automation system effectively helps in saving the time and cost by increased software quality and productivity.

Understandings and Implementations of Continuous Delivery

It was showed that manual testing is still carried out to a substantial level in the industry, and some tasks such as testing the user experience is hard to automate.

Towards a Theory on Architecting for Continuous Deployment

This study looks at the concrete software architecture as a relevant factor for successfully achieving continuous delivery goals and developed a theory that explains the phenomenon of Architecting for Continuous Deployment.

Perceived Benefits of Adopting Continuous Delivery Practices

The results indicate that the adoption of continuous software engineering practices bring various benefits for both customers and developers, beyond mere increased pace of production deployments.

The Impact of DevOps Automation, Controls, and Visibility Practices on Software Continuous Deployment and Delivery

This research provides insights on the three elements of DevOps relevant to automation, visibility, and control practices to identify their impact on continuous deliver and deployment and found that automation does not have a significant impact in continuous delivery and deployment.

Continuous Deployment for Android Applications

The objective is to find out if the introduction automated acceptance tests can be considered enough for continuously deploying software and show that continuous deployment can be implemented successfully by introducing automatedacceptance tests in a context as the one the study was performed in.
...

References

SHOWING 1-10 OF 12 REFERENCES

Climbing the "Stairway to Heaven" -- A Mulitiple-Case Study Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software

A multiple-case study in which barriers associated with the transition towards continuous deployment are explored and key barriers in this transition as well as actions that need to be taken to address these are presented.

Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation

This groundbreaking new book sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users, and introduces state-of-the-art techniques, including automated infrastructure management and data migration, and the use of virtualization.

Continuous Delivery? Easy! Just Change Everything (Well, Maybe It Is Not That Easy)

This experience report describes the journey to continuous delivery with the aim that others can learn from the authors' mistakes and get their teams deploying more frequently.

Experienced Benefits of Continuous Integration in Industry Software Product Development: A Case Study

In this paper, we present a multi-case study of industrial experiences of continuous integration among software professionals working in large scale development projects. In literature, multiple

Prioritizing Unit Test Creation for Test-Driven Maintenance of Legacy Systems

An approach that assists software development and testing managers, who employ TDM, utilize the limited resources they have for testing legacy systems efficiently and suggests that heuristics based on the function size, modification frequency and bug fixing frequency should be used to prioritize the unit test writing of legacy systems.

Agile with Fragile Large Legacy Applications

This paper shares the experience of how three teams with large legacy applications moved from fragile towards agile.

Recommended Steps for Thematic Synthesis in Software Engineering

  • D. CruzesT. Dybå
  • Computer Science
    2011 International Symposium on Empirical Software Engineering and Measurement
  • 2011
This paper conceptualizes the thematic synthesis approach in software engineering as a scientific inquiry involving five steps that parallel those of primary research.

Selected CS articles and columns are also available for free at http://ComputingNow.computer.org. s2lep

  • Selected CS articles and columns are also available for free at http://ComputingNow.computer.org. s2lep

Continuous Deployment at IMVU: Doing the Impossible

  • Fifty Times a Day,” blog,
  • 2009