dc.contributor.author | Mironov, Oleg | |
dc.date.accessioned | 2018-04-17T11:31:34Z | |
dc.date.available | 2018-04-17T11:31:34Z | |
dc.date.issued | 2018 | |
dc.identifier.uri | URN:NBN:fi:amk-201804154700 | |
dc.identifier.uri | http://www.theseus.fi/handle/10024/143357 | |
dc.description.abstract | Software complexity and size are growing at the ever-increasing rate. This study attempts to use modern DevOps practices and technologies to create a reusable pipeline template capable of meeting the demands of modern software and strengthen up the development practices. Such pipeline should largely be reusable and flexible as well as being able to be scaled and maintained with high reliability.
Theoretical research on the topic of how DevOps came to be and what it means is an important part of this project. Then a set of technologies that reflect the state of DevOps today was carefully studied and analysed. Docker and its fast-growing ecosystem is the core technology of this project. With Docker and some other technologies, a set of configuration files could be used to run, develop, test and deploy an application. Such approach allows maximum automation while ensuring transparency of those automation processes.
The result of this project is a fully working pipeline setup that is fully automated and is able to support a fast-paced software development. The pipeline is built against a reference project. Most of the pipeline is configured with a set of different configuration files meaning that from a fresh start it could be brought up with minimal human interaction. It covers all parts of a reference application lifespan from a development environment to a potential production deployment. There is a set of technologies used in the pipeline such as Jenkins, Docker and container orchestration with Rancher. | en |
dc.language.iso | eng | |
dc.publisher | Metropolia Ammattikorkeakoulu | |
dc.rights | Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported | |
dc.title | DevOps Pipeline with Docker | en |
dc.type.ontasot | fi=AMK-opinnäytetyö|sv=YH-examensarbete|en=Bachelor's thesis| | |
dc.identifier.dscollection | 10024/238 | |
dc.organization | Metropolia Ammattikorkeakoulu | |
dc.ccbutton | <a rel="license" target="_blank" href="http://creativecommons.org/licenses/by-nc-sa/3.0/"><img alt="Creative Commons License" style="border-width:0" src="https://publications.theseus.fi/manakin/themes/Theseus/cc/by-nc-sa/3.0/88x31.png"/></a> | |
dc.contributor.organization | Metropolia Ammattikorkeakoulu | |
dc.subject.keyword | Docker | |
dc.subject.keyword | Jenkins | |
dc.subject.keyword | Rancher | |
dc.subject.keyword | DevOps | |
dc.subject.keyword | Pipeline | |
dc.subject.keyword | Automation | |
dc.subject.keyword | Continuous Integration | |
dc.subject.keyword | Continuous Delivery | |
dc.subject.specialization | Software Engineering | |
dc.subject.degreeprogram | fi=Tieto- ja viestintätekniikka|sv=Informations- och kommunikationsteknik|en=Information and Communications Technology| | |
dc.subject.discipline | Degree Programme in Information Technology | |