Automated Capturing and Systematic Usage of DevOps Knowledge for Cloud Applications

Wettinger, Johannes; Andrikopoulos, Vasilios; Leymann, Frank

doi:10.1109/ic2e.2015.23

Cited by 38 publications

(22 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The larger number of challenges, eg, C01, C02, C03, C04, C05, C06, C08, C09, C13, C14, C17, C18, C19, C22, C24, C25, C27, C28, C29, C30, C31, C32, C33, C34, C35, C36, C38, and 41 are about DevOps adoption. ()…”

Section: Resultsmentioning

confidence: 99%

See 1 more Smart Citation

Towards a benefits dependency network for DevOps based on a systematic literature review

Jabbari

Ali

Petersen

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

DevOps as a new way of thinking for software development and operations has received much attention in the industry, while it has not been thoroughly investigated in academia yet. The objective of this study is to characterize DevOps by exploring its central components in terms of principles, practices and their relations to the principles, challenges of DevOps adoption, and benefits reported in the peer-reviewed literature. As a key objective, we also aim to realize the relations between DevOps practices and benefits in a systematic manner. A systematic literature review was conducted. Also, we used the concept of benefits dependency network to synthesize the findings, in particular, to specify dependencies between DevOps practices and link the practices to benefits. We found that in many cases, DevOps characteristics, ie, principles, practices, benefits, and challenges, were not sufficiently defined in detail in the peer-reviewed literature.In addition, only a few empirical studies are available, which can be attributed to the nascency of DevOps research. Also, an initial version of the DevOps benefits dependency network has been derived. The definition of DevOps principles and practices should be emphasized given the novelty of the concept. Further empirical studies are needed to improve the benefits dependency network presented in this study. KEYWORDSbenefits and values, challenges, development and operations, DevOps, principles and practices, systematic literature review

show abstract

Section: Resultsmentioning

confidence: 99%

“…In this regard, Wettinger et al also mention that it is hard to implement holistic DevOps automation for a specific application (C28) due to rapid changes in DevOps automation approaches.…”

Section: Resultsmentioning

confidence: 99%

Towards a benefits dependency network for DevOps based on a systematic literature review

Jabbari

Ali

Petersen

et al. 2018

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

Section: Related Workmentioning

confidence: 92%

“…Our work shares with the work of Wettinger et al the general objective of contributing to ease the discovery of DevOps “knowledge” (which includes Docker images). The aforementioned authors proposed a collaborative approach to store DevOps knowledge in a shared taxonomy‐based knowledge base. More precisely, the aforementioned authors proposed to build the knowledge base in a semiautomated way, by (automatically) crawling heterogeneous artefacts from different sources, and by requiring DevOps experts to share their knowledge and (manually) associate metadata to the artefacts in the knowledge base.…”

Section: Related Workmentioning

confidence: 99%

A microservice‐based architecture for (customisable) analyses of Docker images

2018

View full text Add to dashboard Cite

Summary We introduce DockerAnalyser, a microservice‐based tool that permits building customised analysers of Docker images. The architecture of DockerAnalyser is designed to crawl Docker images from a remote Docker registry, to analyse each image by running an analysis function, and to store the results into a local database. Users can build their own image analysers by instantiating DockerAnalyser with a custom analysis function and by configuring the architecture. More precisely, the steps needed to obtain new analysers are (1) replacing the analysis function used to analyse crawled Docker images, (2) setting the policy for crawling Docker images, and (3) setting the scalability options for obtaining a scalable architecture. In this paper, we also present 2 different use cases, ie, 2 different analysers of Docker images created by instantiating DockerAnalyser with 2 different analysis functions and configuration options. The 2 use cases show that DockerAnalyser decreases the effort required to obtain new analysers versus building them from scratch.

show abstract

“…DevOps is set of practices and principles that is trying to improve life-cycle as a whole through integration between development and operations teams to reduce the release cycles and increase number of software deliveries [4].…”

Section: Introductionmentioning

confidence: 99%

Enhancing Lean Software Development by using Devops Practices

Farid¹,

Helmy²,

Bahloul³

2017

ijacsa

View full text Add to dashboard Cite

Abstract-Competition between companies has made a great pressure to produce new features continuously as fast as possible, subsequently successful software companies needs to learn more about customers and get new features out to them more rapidly. Lean software development cannot integrate between development and operation teams. DevOps enables this merge between them and creates operational parts as one part of the development process and made it up to date during the development phase, so reduced errors during the deployment. The purpose of this paper is to investigate how one can use devOps practices to improve the performance of lean software development production process and introduce a new framework that merge lean and devOps process. The research has been evaluated on a sample of 2 departments in Faculty of Commerce at Helwan University. The results of this work have led to reduce the response delivery time for customers and rapid feedback provides accurate expectations for customer needs that lead to lower levels of deployment pains and lower change fail rates.

show abstract

Automated Capturing and Systematic Usage of DevOps Knowledge for Cloud Applications

Cited by 38 publications

References 7 publications

Towards a benefits dependency network for DevOps based on a systematic literature review

Towards a benefits dependency network for DevOps based on a systematic literature review

A microservice‐based architecture for (customisable) analyses of Docker images

Enhancing Lean Software Development by using Devops Practices

Contact Info

Product

Resources

About