This master's thesis deals with replacement of the servlet container in Jenkins CI with server Undertow. In the thesis, general information about programs, which are related to this topic, are described and current state of the servlet container is analyzed. The result is newly created servlet container for Jenkins CI. Both versions of the Jenkins CI were performance tested and the new version gave better results.

The main of the master's thesis has been to implement a plugin for Jenkins, which enables flow control of launching Jenkins jobs by using business processes. Project jBPM 5, which is based on Business Process Model and Notation 2.0, has been used for business processes. Two sample business processes have been drafted and successfully tested to demonstrate functionality. The main output of this thesis is the jBPM plugin for Jenkins released under free license.

The full enforcement of the General Data Protection Regulation (GDPR) that began on May 25, 2018 forced any organization that collects and/or processes personal data from European Union citizens to comply with a series of stringent and comprehensive privacy regulations. Many software organizations struggled to comply with the entirety of the GDPR's regulations both leading up and even after the GDPR deadline. Previous studies on the subject of the GDPR have primarily focused on finding implications for users and organizations using surveys or interviews. However, there is a dearth of in-depth studies that investigate compliance practices and compliance challenges in software organizations. In particular, small and medium enterprises are often neglected in these previous studies, despite small and medium enterprises representing the majority of organizations in the EU. Furthermore, organizations that practice continuous integration have largely been ignored in studies on GDPR compliance. Using design science methodology, we conducted an in-depth study over the span of 20 months regarding GDPR compliance practices and challenges in collaboration with a small, startup organization. Our first step helped identify our collaborator's business problems. Subsequently, we iteratively developed two artifacts to address those business problems: a set of privacy requirements operationalized from GDPR principles, and an automated GDPR tool that tests these GDPR-derived privacy requirements. This design science approach resulted in five implications for research and for practice about ongoing challenges to compliance. For instance, our research reveals that GDPR regulations can be partially operationalized and tested through automated means, which is advantageous for achieving long term compliance. In contrast, more research is needed to create more efficient and effective means to disseminate and manage GDPR knowledge among software developers. / Graduate

Maintaining quality in software is a difficult task for several reasons, such as, company growth, time-to-market demands, code complexity and more. GUI testing tools and Continuous Integration (CI) are common practice today to tackle some of the issues with maintaining software quality. However, these techniques bring a set of challenges. Visual Regression Testing (VRT) is a special kind of GUI testing technique focused upon image-based assertions. This study presents an implementation and investigation of the benefits and drawbacks of introducing VRT for a CI environment in an industrial context. Additionally, the thesis investigates factors that need to be considered upon this transition. The results show that benefits are associated with this approach, such as, quicker feedback times and an increase in testing frequency. However, drawbacks and implications were also identified, such as, test maintenance and organizational concerns, indicating careful consideration needs to be taken by an organization before proceeding with an implementation.

För att möta kraven på ständiga förändringar har många företag börjat jobba enligt den iterativa, agila modellen Scrum. Denna modell innefattar bl.a. att praktisera kontinuerlig integrering (CI) där utvecklare regelbundet sammanfogar och testar kod. Målet med projektet är att förenkla denna process hos Epiroc i Örebro, så att berörda parter utnyttjar en gemensam CI-portal. Resultatet av projektet är en fungerande webbapplikation som ger Epirocs utvecklare möjlighet att praktisera CI genom att bygga och testa sin kod samt granska resultat från detta i ett modernt och användarvänligt gränssnitt. Vår uppfattning är att drifttsättningen av produkten kommer bidra till återkoppling från användare angående förbättringar. Övergången till kontinuerlig integrering som arbetsprocess hos Epiroc är inte fulländad, många aspekter av applikationens användningsområde är föränderliga. Stor vikt har därför lagts på applikationens modularitet under utvecklingsprocessen vilket ger utrymme för framtida utveckling av applikationen efter Epirocs behov. I dagsläget kan verktyget användas för att starta och övervaka bygg- och testjobb på en Jenkinsserver, men kan i framtiden få en större roll i Epirocs utvecklingskedja, exempelvis som databashanterare för testkodbasen. / Global technological advances are rapid, with this constant change, the demands on companies ability to adapt their digital products constantly increase when rapid changes are to be welcomed and the pace of production increases. To meet the requirements, many companies have started working according to the iterative, agile model Scrum. Part of this model includes practicing continuous integration (CI) where developers continuously merge and test code. The aim of the project is to simplify this process at Epiroc in Örebro, Sweden, so that interested parties are collaborating through a single CI portal. The end result of the project is a working web application that gives developers the opportunity to practice CI by building and testing their code, and review results from this in a modern and user-friendly interface. Commissioning of the application will contribute to input from the users on improvements. The application is modular, which leaves plenty of room for future development.

The procedure of testing the implemented software is important and should be an essential and integrated part of the development process. In order for the testing to be meaningful it is important that the testing procedure ensures that the developed software meet certain requirements. The testing procure is often controlled by some sort of test specification. For many companies it is desirable to automate this procure. The focus of this thesis has been to automate a small subpart of the manual tests today performed related to SAAB:s air traffic management system. The automation has been achieved by studying the existing test specification which involves a lot of manual operations and to write software that mimics a few of these test cases. The thesis has resulted in a test framework which automates a small subset of the manual tests performed today. The framework has been designed to be scalable and to easily allow more test cases to be added by the personnel when time permits. The test framework has also been integrated with SAAB:s existing CI/CD workflow.

Background. Unstable and unpredictable tests, herein referred to as flaky tests, pose a serious challenge to systems in the production environment. If a device is not tested thoroughly, it will be sent back for retesting from the production centers, which is an expensive affair. Removing flaky tests involves detecting the flaky tests, finding the causes of flakiness and finally the elimination of flakiness. The existing literature provides information on causes and elimination techniques of flakiness for software systems. All of these are studied thoroughly, and support is taken from interviews to understand they are applicable in the context of embedded systems. Objectives. The primary objective is to identify causes of flakiness in a device under test and also techniques for eliminating flakiness. Methods. In this paper, we applied a literature review to find the current state-of-art of flakiness. A case study is selected to address the objectives of the study. Interviews and observations carried out to collect data. Data analysis performed using a directed content analysis method. Results. Observations resulted in eliminating 4 causes of flakiness in embedded systems. Interview results in finding 4 elimination techniques which were not found in the literature. Conclusions. Causes and Elimination techniques for the domain of embedded systems are identified. Knowledge translation between the domains was carried out effectively.

No description available.

Software development has gotten more complex and certain parts being more and more automated. Continuous integration practices with automated build and testing greatly benefit the development process. Combined with continuous deployment, the software can go directly from commit to deployment within hours or days which means that every commit is a possible deployment. The ability to trace links between artifacts is known as software traceability which has become a necessity and requirement in the industry. Following these traces and the ability to answer questions and base decisions on them is a complex problem. Tools already used in the industry are hard to adapt since every stakeholder requires different needs. Eiffel protocol aims to be as flexible and scalable as possible to fit as many needs as necessary for the stakeholder. This thesis provides an extension to Eiffel-store, an already existing open-source application that can visualize events in the Eiffel protocol that will be extended with functionality so that it can filter events and answer some questions stakeholders might have.

Source code plagiarism is an ongoing problem in programming courses at higher academic institutions. For this reason, different automated source code plagiarism detection tools have been developed. However, they require several manual steps before the submissions can be compared. Linnaeus University uses GitLab to handle their students’ code-related assignments but lacks an integrated workflow for checking submissions against plagiarism. Instead, Linnaeus University’s plagiarism-checking process is done manually, which is a challenging and time-consuming process. This thesis is a case study on Linnaeus University, focusing on integrating one of the plagiarism detection tools with GitLab using Continuous integration pipelines. The objectives have been to collect students’ submissions, communicate with the plagiarism tool, and visually present the results within GitLab. The prototype has been evaluated by a set of manually created submissions with different levels of plagiarism to ensure that the detection tool differentiates plagiarized and non-plagiarized submissions. Teachers at Linnaeus University have tested the workflow and reasoned whether the prototype fulfills their requirements.