Implementation of Continuous Delivery Systems
Permanent address of the item is
Jatkuvien toimitusjärjestelmien toteutus
Continuous Integration, Delivery, and Deployment are subjects that have been on the table in the recent years. The books Continuous Integration by Duvall et. al (2007), and Continuous Delivery by Humble et. al (2010) are, however, the only extensive literature that has been published on the subject. In addition to the books there is information available based on miscellaneous conferences and scientific publishments, but this information is fairly scattered and hard to compile. A lot of companies suffer from long delays between implementing and delivering software features. Multiple parties ranging from foreign developers to Finnish leader projects have researched the benefits that can be gained from automating and making software delivery continuous. Benefits include among other things rapid customer feedback, lowered production delivery costs and delays, and smaller number of errors in processes. Companies do, however, have difficulties in implementing Continuous Integration, Delivery, and Deployment. This is mainly due to the arbitrarity of the work. There is information available on the subject, but collecting, studying, and distributing that information can be very costly. This Master of Science thesis researches the implementation a Continuous Delivery system in a Finnish software company. The research work is done in an internal project, and the aim is to implement a generic software build, test, and delivery system. The process involves gathering business, technical, and user requirements, compiling a requirements definition, designing a phased project plan, and executing that plan to implement a Continuous Delivery system on top of the AWS cloud platform.