ADEPT: A Socio-Technical Theory of Continuous Integration

@article{Elazhary2021ADEPTAS,
  title={ADEPT: A Socio-Technical Theory of Continuous Integration},
  author={Omar Elazhary and Margaret-Anne D. Storey and Neil A. Ernst and Elise Paradis},
  journal={2021 IEEE/ACM 43rd International Conference on Software Engineering: New Ideas and Emerging Results (ICSE-NIER)},
  year={2021},
  pages={26-30}
}
  • Omar Elazhary, M. Storey, Elise Paradis
  • Published 13 February 2021
  • Computer Science
  • 2021 IEEE/ACM 43rd International Conference on Software Engineering: New Ideas and Emerging Results (ICSE-NIER)
Continuous practices that rely on automation in the software development workflow have been widely adopted by industry for over a decade. Despite this widespread use, software development remains a primarily human-driven activity that is highly creative and collaborative. There has been extensive research on how continuous practices rely on automation and its impact on software quality and development velocity, but relatively little has been done to understand how automation impacts developer… 

Figures from this paper

Investigating the Interplay between Developers and Automation

  • Omar Elazhary
  • Computer Science
    2021 IEEE/ACM 43rd International Conference on Software Engineering: Companion Proceedings (ICSE-Companion)
  • 2021
TLDR
The ADEPT theory of developers and automation is presented, in an attempt to bridge the gap and identify the possible ways context, process, and other factors may influence how developers perceive, interpret, and interact with automation.

References

SHOWING 1-10 OF 32 REFERENCES

Uncovering the Benefits and Challenges of Continuous Integration Practices

TLDR
It is shown that how CI is implemented varies, and thus studying CI (for example, using data mining) requires understanding these differences as important context for research studies.

Quality and productivity outcomes relating to continuous integration in GitHub

TLDR
The main finding is that continuous integration improves the productivity of project teams, who can integrate more outside contributions, without an observable diminishment in code quality.

The impact of continuous integration on other software development practices: A large-scale empirical study

TLDR
The adaptation and evolution of code writing and submission, issue and pull request closing, and testing practices as Travis CI is adopted by hundreds of established projects on GitHub are studied to suggest a more nuanced picture of how GitHub teams are adapting to, and benefiting from, continuous integration technology.

Continuous software engineering: A roadmap and agenda

Theory-oriented software engineering

Use and Misuse of Continuous Integration Features: An Empirical Study of Projects That (Mis)Use Travis CI

TLDR
A study of feature use and misuse in 9,312 open source systems that use Travis CI reveals that explicit deployment code is rare and proposes Gretel—an anti-pattern removal tool for Travis CI specifications, which can remove 69.60 percent of the most frequently occurring anti- pattern automatically.

Usage, costs, and benefits of continuous integration in open-source projects

TLDR
Evidence is shown that supports the claim that CI helps projects release more often, that CI is widely adopted by the most popular projects, as well as finding that the overall percentage of projects using CI continues to grow, making it important and timely to focus more research on CI.

An empirical characterization of bad practices in continuous integration

TLDR
This paper empirically investigates what are the bad practices experienced by developers applying Continuous Integration, and compiled a catalog of 79 CI bad smells belonging to 7 categories related to different dimensions of a CI pipeline management and process.

Cinders: the continuous integration and delivery architecture framework

This extended abstract summarizes an article, which has been published in Information and Software Technology and was selected for the Journal-First presentations at the International Conference on

Automated Reporting of Anti-Patterns and Decay in Continuous Integration

TLDR
It is argued that automated detection can help with early identification of CI anti-patterns and prevent such a process decay and built CI-Odor, a reporting tool for CI processes that detects the existence of four relevant anti- patterns by analyzing regular build logs and repository information.