The effects of continuous integration on software development: a systematic literature review

Soares, Eliezio; Sizílio, Gustavo; Santos, J.; Alencar, D. S. M.; Kulesza, Uirá

doi:10.1007/s10664-021-10114-1

Cited by 21 publications

(5 citation statements)

References 40 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Definition number of repo builds [75] Total number of builds project in the project number of devops artefacts Total number of DevOps artefacts in the project project maturity [62,55] Number of days since the first build was made recent failure rate Failure rate of last five builds in the project commits per build Average number of commits per build in the project number of devops authors [4] Total number of DevOps developers in the project forks [62,55,4] Total number of forks on GitHub 5 repo skewness Skewness of developer contributions to DevOps in the project…”

Section: Featurementioning

confidence: 99%

“…While CI is advantageous for projects, other studies revealed the difficulties of adopting CI. Among the several challenges that come with CI, build failures are a challenge that is unavoidable for many projects [60,59,83,45,52,84,76,25]. For example, Kerzazi et al [45] analyzed 3,214 builds produced in a large software company over a period of 6 months.…”

Section: Continuous Integration (Ci)mentioning

confidence: 99%

See 1 more Smart Citation

The Impact of Code Ownership of DevOps Artefacts on the Outcome of DevOps CI Builds

Kola-Olawuyi,

Weeraddana,

Nagappan

2024

Proceedings of the 21st International Conference on Mining Software Repositories

View full text Add to dashboard Cite

show abstract

Section: Featurementioning

confidence: 99%

Section: Continuous Integration (Ci)mentioning

confidence: 99%

The Impact of Code Ownership of DevOps Artefacts on the Outcome of DevOps CI Builds

Kola-Olawuyi,

Weeraddana,

Nagappan

2024

Proceedings of the 21st International Conference on Mining Software Repositories

View full text Add to dashboard Cite

show abstract

“…This enables developers to focus on writing code and tests in their IDE, while the CI system performs analyses and provides a summary of findings and uncovered code [44]. The use of CI platforms has been shown to improve productivity and enable faster software releases with higher quality [43,52].…”

Section: Background 21 Software Testingmentioning

confidence: 99%

Gamekins: Gamifying Software Testing in Jenkins

Straubinger,

Fraser

2022

2022 IEEE/ACM 44th International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)

View full text Add to dashboard Cite

Testing plays a crucial role in software development, and it is essential for software engineering students to receive proper testing education. However, motivating students to write tests and use automated testing during software development can be challenging. To address this issue and enhance student engagement in testing when they write code, we propose to incentivize students to test more by gamifying continuous integration. For this we use Gamekins, a tool that is seamlessly integrated into the Jenkins continuous integration platform and uses game elements based on commits to the source code repository: Developers can earn points by completing test challenges and quests generated by Gamekins, compete with other developers or teams on a leaderboard, and receive achievements for their test-related accomplishments. In this paper, we present our integration of Gamekins into an undergraduate-level course on software testing. We observe a correlation between how students test their code and their use of Gamekins, as well as a significant improvement in the accuracy of their results compared to a previous iteration of the course without gamification. As a further indicator of how this approach improves testing behavior, the students reported enjoyment in writing tests with Gamekins. CCS CONCEPTS• Software and its engineering → Software testing and debugging; • Social and professional topics → Software engineering education.

show abstract

“…They face difficulties meeting deadlines and customers' requirements, both in terms of functionality and quality. Existing research shows that SD organizations have difficulties using SDMs (Conboy & Carroll, 2019;Dikert et al, 2016;Soares et al, 2022).…”

Section: Introductionmentioning

confidence: 99%

Business Strategy and Agile Software Development Methods Alignment in Startup Companies: Cases of Five Swedish Startups

Aasi,

Berggren-Lagercrantz,

Kökmen

2024

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

Misinterpretations and faulty use of Software Development Method (SDM) practices and principles are identified pitfalls in Software Development (SD). Previous research indicates cases with method adoption and use failures; one reason could be the SDM Cargo Cult (CC) behavior, where SD organizations claim to be agile but not doing agile. Previous research has suggested the SDM CC framework as an analytical tool. The aim of this paper is to refine the SDM CC framework and empirically test this version of the framework. We use data from an ethnographical study on three SD teams' Daily Scrum Meetings (DSM). The empirical material was collected through observations, interviews, and the organization's business documents. We uncovered twelve CC situations in the SD teams' use of the DSM practice, structured into seven categories of SDM deviations: bringing irrelevant information, canceling meetings, disturbing the team, receiving unclear information, bringing new requirements, problemsolving, and task distribution.

show abstract

The effects of continuous integration on software development: a systematic literature review

Cited by 21 publications

References 40 publications

The Impact of Code Ownership of DevOps Artefacts on the Outcome of DevOps CI Builds

The Impact of Code Ownership of DevOps Artefacts on the Outcome of DevOps CI Builds

Gamekins: Gamifying Software Testing in Jenkins

Business Strategy and Agile Software Development Methods Alignment in Startup Companies: Cases of Five Swedish Startups

Contact Info

Product

Resources

About