Line 7: | Line 7: | ||
== Full document == | == Full document == | ||
− | <pdf>Media:Plakidas_et_al_2019a- | + | <pdf>Media:Plakidas_et_al_2019a-beopen463-7104-document.pdf</pdf> |
DevOps and Continuous Delivery (CD) are becoming the de-facto standard for software deployment in the cloud. Deployment pipelines are a core artefact in such practices, but so far their design is largely discussed informally, and existing sources on DevOps and CD practices are often inconsistent or incomplete. The lack of a generic, complete, tool-agnostic, and application-independent treatment of deployment pipeline design and architecture impedes their understanding by human designers and the creation of generic tools that work across different technologies and applications. To alleviate this problem, we have performed a qualitative, in-depth study of 25 deployment practice descriptions by practitioners containing informal deployment pipeline models. From our study we derived a precisely specified model of deployment pipeline architectures. We can show that the formal model substantially increases the precision of the modelling compared to the informally modelled pipelines in the original sources.
Document type: Conference object
The different versions of the original document can be found in:
under the license http://creativecommons.org/licenses/by/4.0/legalcode
DOIS: 10.5281/zenodo.2671625 10.5281/zenodo.3476556 10.5281/zenodo.2790643 10.5281/zenodo.2790644 10.5281/zenodo.2671624 10.1109/scc.2019.00033
Published on 01/01/2019
Volume 2019, 2019
DOI: 10.5281/zenodo.2671625
Licence: Other
Are you one of the authors of this document?