Do developers fix continuous integration smells?

Simple item page
buir.contributor.authorYaşa, Ayberk
buir.contributor.authorErgül, Ege
buir.contributor.authorTüzün, Eray
buir.contributor.orcidErgül, Ege|0009-0001-7258-9374
buir.contributor.orcidTüzün, Eray|0000-0002-5550-7816
dc.citation.epage21en_US
dc.citation.spage12
dc.contributor.authorYaşa, Ayberk
dc.contributor.authorErgül, Ege
dc.contributor.authorErdoğmus, H.
dc.contributor.authorTüzün, Eray
dc.coverage.spatialCA, San Francisco, USA
dc.date.accessioned2024-03-07T13:16:54Z
dc.date.available2024-03-07T13:16:54Z
dc.date.issued2023-12-08
dc.departmentDepartment of Computer Engineering
dc.descriptionConference Name: PROMISE 2023: Proceedings of the 19th International Conference on Predictive Models and Data Analytics in Software Engineering
dc.descriptionDate of Conference: 8 December 2023
dc.description.abstractContinuous Integration (CI) is a common software engineering practice in which the code changes are frequently merged into a software project repository after automated builds and tests have been successfully run. CI enables developers to quickly detect bugs, enhance the quality of the code, and shorten review times. However, developers may encounter some obstacles in following the CI principles. They may be unaware of them, they may follow the principles partially or they may even act against them. These behaviors result in CI smells. CI smells may in turn lessen the benefits of CI. Addressing CI smells rapidly allows software projects to fully reap the benefits of CI and increase its effectiveness. The main objective of this study is to investigate how frequently developers address CI smells. To achieve this objective, we first selected seven smells, then implemented scripts for detecting these smells automatically, and then ran the scripts in eight open-source software projects using GitHub Actions. To assess the resolution extent of CI smells by practitioners, we calculated the occurrences and time-to-resolution (TTR) of each smell. Our results suggest that Skipped Job smell has been fixed slightly more than other CI smells. The most frequently observed smell was Long Build, which was detected in an average of 19.03% of all CI builds. Fake Success smell does not get resolved in projects where it exists. Our study reveals that practitioners do not fix CI smells in practice. Further studies are needed to explore the underlying reasons behind this, in order to recommend more effective strategies for addressing these smells.
dc.description.provenanceMade available in DSpace on 2024-03-07T13:16:54Z (GMT). No. of bitstreams: 1 Do_developers_fix_continuous_integration_smells.pdf: 3170643 bytes, checksum: 9bed87d605c7af638082a6e3807c647c (MD5) Previous issue date: 2023-12-08en
dc.identifier.doi10.1145/3617555.3617870
dc.identifier.isbn9798400703751
dc.identifier.urihttps://hdl.handle.net/11693/114392
dc.language.isoen
dc.publisherAssociation for Computing Machinery
dc.relation.isversionofhttps://dx.doi.org/10.1145/3617555.3617870
dc.source.titleACM International Conference Proceeding Series
dc.subjectContinuous integration
dc.subjectContinuous integration smells
dc.subjectCIsmell
dc.subjectAnti-patterns
dc.subjectSmell detection
dc.subjectProcess smells
dc.titleDo developers fix continuous integration smells?
dc.typeConference Paper

Files

Original bundle
Now showing 1 - 1 of 1
Thumbnail Image
Name:
Do_developers_fix_continuous_integration_smells.pdf
Size:
3.02 MB
Format:
Adobe Portable Document Format
Download
License bundle
Now showing 1 - 1 of 1
No Thumbnail Available
Name:
license.txt
Size:
2.01 KB
Format:
Item-specific license agreed upon to submission
Description:
Download

Collections

Department of Computer Engineering