The Top 10 Adages in Continuous Deployment

Parnin, Chris; Helms, Eric; Atlee, Chris; Boughton, Harley; Ghattas, Mark; Glover, Andy; Holman, James; Micco, John; Murphy, Brendan; Savor, Tony; Stumm, Michael; Whitaker, Shari; Williams, Laurie

doi:10.1109/ms.2017.86

Cited by 75 publications

(40 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Interest in the practice of IaC have grown amongst both: practitioners [3] and researchers [5] [6]. As shown in Figure 1, Google Trend 5 data related to the search term 'Infrastructure as Code', provides further evidence on how IaC as a topic has a growing interest.…”

Section: Introductionmentioning

confidence: 91%

“…Popular IaC technologies, such as Chef 1 and Puppet 2 , provide utilities to automatically configure and provision software deployment infrastructure using cloud instances. Information technology (IT) organizations such as, Ambit Energy [2], Github 3 , Mozilla [3], and Netflix [3] use these utilities to provision cloud-based instances, such as Ama-1 https://www.chef.io/chef/ 2 https://puppet.com/ 3 https://speakerdeck.com/kpaulisse/puppetconf-2016-scaling-puppet-and-puppet-culture-atgithub zon Web Services (AWS) 4 , managing databases, and managing user accounts both on local and remote computing instances. For example, Puppet provides the 'sshkey resource' to install and manage secure shell (SSH) host keys and the 'service resource' to manage software services automatically [4].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

A systematic mapping study of infrastructure as code research

Rahman¹,

Mahdavi-Hezaveh²,

Williams³

2019

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Context: Infrastructure as code (IaC) is the practice to automatically configure system dependencies and to provision local and remote instances. Practitioners consider IaC as a fundamental pillar to implement DevOps practices, which helps them to rapidly deliver software and services to end-users. Information technology (IT) organizations, such as Github, Mozilla, Facebook, Google and Netflix have adopted IaC. A systematic mapping study on existing IaC research can help researchers to identify potential research areas related to IaC, for example, the areas of defects and security flaws that may occur in IaC scripts.Objective: The objective of this paper is to help researchers identify research areas related to infrastructure as code (IaC) by conducting a systematic mapping study of IaC-related research.Methodology: We conduct our research study by searching six scholar databases.We collect a set of 33,887 publications by using seven search strings. By systematically applying inclusion and exclusion criteria, we identify 31 publications related to IaC. We identify topics addressed in these publications by applying qualitative analysis. Results:We identify four topics studied in IaC-related publications: (i) framework/tool for infrastructure as code; (ii) use of infrastructure as code; (iii) em-pirical study related to infrastructure as code; and (iv) testing in infrastructure as code. According to our analysis, 52% of the studied 31 publications propose a framework or tool to implement the practice of IaC or extend the functionality of an existing IaC tool.Conclusion: Our findings suggest that framework or tools is a well-studied topic in IaC research. As defects and security flaws can have serious consequences for the deployment and development environments in DevOps, along with other topics, we observe the need for research studies that will study defects and security flaws for IaC.

show abstract

Section: Introductionmentioning

confidence: 91%

Section: Introductionmentioning

confidence: 99%

A systematic mapping study of infrastructure as code research

Rahman¹,

Mahdavi-Hezaveh²,

Williams³

2019

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

show abstract

“…This category includes factors that are directly related to people. The situational factors included in this category are team, team interaction, reviewer response, and knowledge sharing [17], [19], [26], [34], [41], [42], [43], [44], [45], [46], [47], [48].…”

Section: ) Peoplementioning

confidence: 99%

Situational Factors for Modern Code Review to Support Software Engineers’ Sustainability

Nazir¹,

Fatima²,

Chuprat³

2020

IJACSA

View full text Add to dashboard Cite

Software engineers working in Modern Code Review (MCR) are confronted with the issue of lack of competency in the identification of situational factors. MCR is a software engineering activity for the identification and fixation of defects before the delivery of the software product. This issue can be a threat to the individual sustainability of software engineers and it can be addressed by situational awareness. Therefore, the objective of the study is to identify situational factors concerning the MCR process. Systematic Literature Review (SLR) has been used to identify situational factors. Data coding along with continuous comparison and memoing procedures of grounded theory and expert review has been used to produce an exclusive and validated list of situational factors grouped under categories. The study results conveyed 23 situational factors that are grouped into 5 broad categories i.e. People, Organization, Technology, Source Code and Project. The study is valuable for researchers to extend the research and for software engineers to identify situations and sustain for longer.

show abstract

“…Similar to software source code, the codebase for IaC scripts in an IT organization can be large, containing hundreds of lines of code [4]. IaC scripts are susceptible to human errors [3] and bad coding practices [5], which can eventually introduce defects in IaC scripts [6] [3]. Defects in IaC scripts can have serious consequences for IT organizations who rely on IaC scripts to ensure reliability of the constructed automated deployment pipelines.…”

Section: Introductionmentioning

confidence: 99%

Source code properties of defective infrastructure as code scripts

Rahman

Williams

2019

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Context: In continuous deployment, software and services are rapidly deployed to end-users using an automated deployment pipeline. Defects in infrastructure as code (IaC) scripts can hinder the reliability of the automated deployment pipeline.We hypothesize that certain properties of IaC source code such as lines of code and hard-coded strings used as configuration values, show correlation with defective IaC scripts.Objective: The objective of this paper is to help practitioners in increasing the quality of infrastructure as code (IaC) scripts through an empirical study that identifies source code properties of defective IaC scripts.Methodology: We apply qualitative analysis on defect-related commits mined from open source software repositories to identify source code properties that correlate with defective IaC scripts. Next, we survey practitioners to assess the practitioner's agreement level with the identified properties. We also construct defect prediction models using the identified properties for 2,439 scripts collected from four datasets.Results: We identify 10 source code properties that correlate with defective IaC scripts. Of the identified 10 properties we observe lines of code and hard-coded string to show the strongest correlation with defective IaC scripts. Hard-coded string is the property of specifying configuration value as hard-coded string. According to our survey analysis, majority of the practitioners show agreement for two properties: include, the property of executing external modules or scripts, and hard-coded string. Using the identified properties, our constructed defect prediction models show a precision of 0.70∼0.78, and a recall of 0.54∼0.67.Conclusion: Based on our findings, we recommend practitioners to allocate sufficient inspection and testing efforts on IaC scripts that include any of the identified 10 source code properties of IaC scripts.

show abstract

The Top 10 Adages in Continuous Deployment

Cited by 75 publications

References 6 publications

A systematic mapping study of infrastructure as code research

A systematic mapping study of infrastructure as code research

Situational Factors for Modern Code Review to Support Software Engineers’ Sustainability

Source code properties of defective infrastructure as code scripts

Contact Info

Product

Resources

About