Build systems are widely used in today's software projects to automate integration and build
processes. Similar to source code, build specifications need to be maintained to avoid …

Continuous integration (CI) is a widely used practice in modern software engineering.
Unfortunately, it is also an expensive practice---Google and Mozilla estimate their CI …

Continuous Integration (CI) and Continuous Delivery (CD) are widespread in both industrial
and open-source software (OSS) projects. Recent research characterized build failures in CI …

Release engineers are continuously required to de-liver high-quality software products to
the end-user. As a result, modern software companies are proposing new changes in their …

Long build times in continuous integration (CI) can greatly increase the cost in human and
computing resources, and thus become a common barrier faced by software organizations …

Modern code review (MCR) is nowadays well-adopted in industrial and open source
projects. Recent studies have investigated how developers perceive its ability to foster code …

Background: Code review is a well-established software quality practice where developers
critique each others' changes. A shift towards automated detection of low-level issues (eg …

Automated builds, which may pass or fail, provide feedback to a development team about
changes to the codebase. A passing build indicates that the change compiles cleanly and …

When collaborating, developers often create and change software artifacts without being
fully aware of team members' work. While such independence is essential for increasing …

Continuous Integration (CI) is a widely-used software development practice to reduce risks.
CI builds often break, and a large amount of efforts are put into troubleshooting broken …