The elderly social care IT company Phoniro is developing solutions for deploying software using docker technologies. To secure quality in their deploy pipelines Phoniro would like to do automatic selenium testing within Docker containers. The project should set the framework and required technical solution to enable this and also run some basic test including suitable reporting on test success. This is a concept that is new to Phoniro that would allow them, if proven, to automate testing in a safe environment, and pushing their web applications to deployment faster. The purpose is to prove this concept by creating a framework that will easily let the user run web applications inside a Docker container. Then run this framework inside of a pipeline to see the testing capabilities. The user is supposed to be able to do this without any previous knowledge of how docker works. We have developed a framework in Python that enables the user to build and run their web application inside a docker container. We built a pipeline and connected it to the repository with the source code for the web application. The framework is run inside the pipeline to start the container, followed by simple selenium tests that we created to test the concept. We have proven the concept to run and test web applications in docker containers inside of pipelines to work. It is possible connect a web application in development to a repository, connect it to a pipeline and have it automatically test the application every time a change is made to the source code. By designing proper selenium tests the pipeline can save a lot of time and effort that is otherwise spent on manual testing

Continuous delivery is a software development methodology that aims to reduce development cycle time by putting a strong emphasis on automation, quality and rapid feedback. This thesis develops an automated method for detecting performance regressions as part of a continuous delivery deployment pipeline. The chosen method is based on control charts, a tool commonly used within statistical process control. This method is implemented as part of a continuous delivery deployment pipeline and its ability to detect performance regressions is then evaluated by injecting various performance bottlenecks in a sample application. The results from this thesis show that using a control chart based approach is a viable option when trying to automate verification of load test results in the context of continuous delivery. / Kontinuerlig leverans är en utvecklingsmetodik för mjukvara med målet att reducera ledtid genom att fokusera på automatisering, kvalitet och snabb återkoppling. I det här examensarbetet utvecklas en automatiserad metod för att upptäcka försämringar i prestanda i en deployment pipeline för kontinuerlig leverans. Den valda metoden baseras på kontrolldiagram, ett verktyg som ofta används inom statistisk processkontroll. Metoden implementeras som en del av en deployment pipeline för kontinuerlig leverans och dess förmåga att upptäcka prestandaförsämringar utvärderas genom att olika prestandarelaterade flaskhalsar implementeras i en testapplikation. Resultaten från arbetet visar att en metod baserad på kontrolldiagram är ett tänkbart alternativ för att automatisera verifiering lasttestresultat inom kontinuerlig leverans.

In the world of software development, there is an increasing demand for software to keep up with rapid changes in its real-world context. A Resilient Digital Twin of an Organization is a type of software whose purpose is to digitally represent an organization or a component of an organization - as a Digital Twin -, and to keep doing so accurately throughout the real-world organization’s changes - a Resilient Digital Twin. An architectural pattern, called the EA Blueprint Pattern, has recently been proposed as a pattern to use for developing Resilient Digital Twins that can change together with the changes in the organization. However, software architecture is not the only factor that enables continuous change and adaptability in software. For software development teams to be able to deliver software rapidly and reliably, the software development process itself must be adapted to allow for frequent and fast changes. From this need, the Agile methodology and subsequently the set of work practises called DevOps has emerged. DevOps leverages automation and fast feedback as tools to facilitate a shorter system development life cycle and continuous delivery. The usage of DevOps is becoming increasingly popular in the software development field. It stands to reason that there is a need to ensure that the EA Blueprint Pattern is appropriate even in a DevOps context, where different tools and routines may be used than in traditional development. To complete this project, a use case of the EA Blueprint Pattern has been moved from a traditionally developed and deployed setting to a DevOps setting that includes essential DevOps tools such as Infrastructure as Code, a cloud environment, and a CI/CD pipeline that enables automatic deployment and therefore a shorter system development life cycle. By doing this, it can be gauged how well the EA Blueprint Pattern is adapted to a modern software development process which utilises the advantages of DevOps.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-03-16T12:48:08Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Filipe_Versao_Final_Pos_Defesa_Deposito.pdf: 1855793 bytes, checksum: 366a64a51c618d78933bc62349a182cc (MD5) / Made available in DSpace on 2016-03-16T12:48:08Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Filipe_Versao_Final_Pos_Defesa_Deposito.pdf: 1855793 bytes, checksum: 366a64a51c618d78933bc62349a182cc (MD5) Previous issue date: 2015-08-21 / Hoje as organizações de T.I. estão enfrentando um sério desafio, por um lado temos mercados cada vez mais competitivos, com mudanças quase que rotineiras nos softwares e uma variedade imensa de dispositivos e sistemas operacionais; por outro, os sistemas ficam cada vez mais complexos, integrados a outros serviços e exigindo um alto grau de confiabilidade e disponibilidade dos mesmos, exigindo assim um processo de implantação cada vez mais eficiente e robusto. Nos últimos anos o termo DevOps – colaboração entre desenvolvimento e operação - e suas práticas foram amplamente usados e discutidos sob diferentes aspectos. Assim como no movimento ágil, DevOps também nasceu na indústria e a partir da necessidade da mesma. Por mais que várias organizações já adotem práticas que ficaram conhecidas como DevOps, seu uso ainda não é prescritivo, existindo assim uma variedade de diferentes manifestações de uso em termos de definição e padrão dentre as organizações. Diante disso, esta dissertação teve por objetivo realizar um mapeamento sistemático da literatura e um survey em busca do movimento DevOps, áreas de concentração dos estudos, os principais autores da área e as principais práticas e formas de uso de DevOps nas organizações. Como contribuição, esta pesquisa identificou que dentre as principais áreas de DevOps podem-se destacar (i) entrega, (ii) integração, (iii) e testes contínuos, além da (vi) automação da infraestrutura. Como principais práticas foram possíveis destacar: (a) implantações através de máquinas virtuais, (b) visibilidade do pipeline de implantação, (c) processos robustos de roolbacks, além de técnicas como (d) canary release, (e) toogled features e (f) blue-green deployments. / Today's IT organizations are facing a serious challenge, on the one hand we increasingly competitive markets with routine software’s changes and a wide variety of devices and operating systems; on the other hand, the systems are increasingly complex, integrated with other services and requiring a high degree of reliability and availability requiring a deploy process increasingly efficient and robust. In recent years the DevOps term - a clipped compound of development and operations - and DevOps’s practices were widely used and discussed under different aspects. As agile movement, the DevOps term was also born in the industry’s need. Today many organizations already adopt practices that became known as DevOps its use is not prescriptive, so there is a variety of different manifestations of use in terms of definition and standard among organizations. Therefore, this work aimed to carry out a mapping study and a survey in search of the state of the art DevOps movement, concentration areas of study, the main authors of the area and the main practices and the use of DevOps in organizations. As a contribution, this research found that among the main DevOps area can highlight: (i) continuous delivery; (ii) continuous integration; (iii) continuous testing; and (vi) infrastructure’s automation. Additionally, we can emphasize the main practices in the DevOps adoption: (a) deploys through virtual machines; (b) visibility’s deployment pipeline; (c) robust processes roolbacks, and techniques such as (d) canary release, (e) toogled features and (f) blue-green deployments.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2016-03-16T14:48:51Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Filipe_Versao_Final_Pos_Defesa_Deposito.pdf: 1855793 bytes, checksum: 366a64a51c618d78933bc62349a182cc (MD5) / Made available in DSpace on 2016-03-16T14:48:52Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Filipe_Versao_Final_Pos_Defesa_Deposito.pdf: 1855793 bytes, checksum: 366a64a51c618d78933bc62349a182cc (MD5) Previous issue date: 2015-08-21 / Hoje as organizações de T.I. estão enfrentando um sério desafio, por um lado temos mercados cada vez mais competitivos, com mudanças quase que rotineiras nos softwares e uma variedade imensa de dispositivos e sistemas operacionais; por outro, os sistemas ficam cada vez mais complexos, integrados a outros serviços e exigindo um alto grau de confiabilidade e disponibilidade dos mesmos, exigindo assim um processo de implantação cada vez mais eficiente e robusto. Nos últimos anos o termo DevOps – colaboração entre desenvolvimento e operação - e suas práticas foram amplamente usados e discutidos sob diferentes aspectos. Assim como no movimento ágil, DevOps também nasceu na indústria e a partir da necessidade da mesma. Por mais que várias organizações já adotem práticas que ficaram conhecidas como DevOps, seu uso ainda não é prescritivo, existindo assim uma variedade de diferentes manifestações de uso em termos de definição e padrão dentre as organizações. Diante disso, esta dissertação teve por objetivo realizar um mapeamento sistemático da literatura e um survey em busca do movimento DevOps, áreas de concentração dos estudos, os principais autores da área e as principais práticas e formas de uso de DevOps nas organizações. Como contribuição, esta pesquisa identificou que dentre as principais áreas de DevOps podem-se destacar (i) entrega, (ii) integração, (iii) e testes contínuos, além da (vi) automação da infraestrutura. Como principais práticas foram possíveis destacar: (a) implantações através de máquinas virtuais, (b) visibilidade do pipeline de implantação, (c) processos robustos de roolbacks, além de técnicas como (d) canary release, (e) toogled features e (f) blue-green deployments. / Today's IT organizations are facing a serious challenge, on the one hand we increasingly competitive markets with routine software’s changes and a wide variety of devices and operating systems; on the other hand, the systems are increasingly complex, integrated with other services and requiring a high degree of reliability and availability requiring a deploy process increasingly efficient and robust. In recent years the DevOps term - a clipped compound of development and operations - and DevOps’s practices were widely used and discussed under different aspects. As agile movement, the DevOps term was also born in the industry’s need. Today many organizations already adopt practices that became known as DevOps its use is not prescriptive, so there is a variety of different manifestations of use in terms of definition and standard among organizations. Therefore, this work aimed to carry out a mapping study and a survey in search of the state of the art DevOps movement, concentration areas of study, the main authors of the area and the main practices and the use of DevOps in organizations. As a contribution, this research found that among the main DevOps area can highlight: (i) continuous delivery; (ii) continuous integration; (iii) continuous testing; and (vi) infrastructure’s automation. Additionally, we can emphasize the main practices in the DevOps adoption: (a) deploys through virtual machines; (b) visibility’s deployment pipeline; (c) robust processes roolbacks, and techniques such as (d) canary release, (e) toogled features and (f) blue-green deployments.