Ways to improve Continuous Deployment processes
Loading...
URL
Journal Title
Journal ISSN
Volume Title
Perustieteiden korkeakoulu |
Master's thesis
Unless otherwise stated, all rights belong to the author. You may download, display and print this publication for Your own personal use. Commercial use is prohibited.
Authors
Date
2020-03-16
Department
Major/Subject
Software and Service Engineering
Mcode
SCI3043
Degree programme
Master’s Programme in Computer, Communication and Information Sciences
Language
en
Pages
62 + 18
Series
Abstract
Modern software development forces companies to release high quality software faster to respond to market needs. These requirements force software companies to invest on processes which make them able to make development faster without losing quality. Continuous deployment is becoming popular practice to answer the market needs, but using it efficiently can be hard. In this thesis we investigate the benefits, problems and best practices relating to continuous deployment using a literature review and a case study. The objective of this research is to identify the benefits of continuous deployment, and to discover which problems and best practices occur in our case organization, and how often. We investigate a case organization by using interviews and a survey for software professionals. Our main finding is that continuous deployment is the preferred way to do software development and it has numerous benefits. Our case study identified a number of problems which harm the development work. Lack of automated tests and schedule pressures were the most often happening problems. We identified numerous best practices but none of them was used often. These practices included for example techniques which improved test automation practices and organizational support methods for the development team. Future research could focus on why the problems occur often, and why best practices are not widely used.Description
Supervisor
Vanhanen, JariThesis advisor
Haglund, NilsKeywords
continuous integration, continuous delivery, continuous deployment, empirical software engineering