Continuous delivery

Abstract

[en] The project consists in researching, analyzing and implementing a deployment pipeline from scratch. During the implementation, a web-application called Funny Stories is created to demonstrate the way this kind of system works. To develop this system, a series of technologies were used. For the implementation of the application the tools used were Java 8 with the framework Spring Boot for the server side; HTML, jQuery, Bootstrap and CSS for the client side, and MySQL for managing the database. The web-site allows users to visualize stories posted by other people which are sorted by categories. They are also able to use a voting system to give their feedback for each post. The web-site is public and these features can be accessed by anyone. When integrating new features into an application and the process is manual, a lot of unforeseen error can happen which can end up delaying the delivery of the software by hours or days. This result in the developer not being able to show his work and delaying the release process which can affect the end users since they cannot use the product. A lot of pressure is put on the responsible for the integration and can end up in a lot of frustration. These problems are very common inside organizations and have inevitable outcome in the development process. These are indications that something is not right because the delivery should be fast and repeatable. This project looks at the delivery from another perspective and will present a series of practices which will improve the code integration. This will allow the developers to release their work several times a day while reducing the risks of the process. The release management of this application is done by using an automated deployment pipeline. This implies that whenever there is a change to the system, the deployment pipeline automatically rebuilds the entire application, tests it for errors and deploys it to the production environment.