spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

Why Software Builds Fail and Areas for Improvement

Written by SPK Blog Post
Published on June 29, 2015

In a recently published paper, researchers at Google examined the issue of failed software builds within their organization. Specifically, they wanted to address the separate questions of “How often do builds fail?”, “Why do builds fail”, and “How long does it take to fix broken builds?” To answer these questions, the researchers looked at 26.6 million Java and C++ builds due to the overwhelming usage of these two languages within Google. For the purposes of this article, we will review the results of the question “why do builds fail?”

To determine why builds were failing, the researchers examined the build logs and categorized compiler error messages into different groups. Of the categories defined, the researchers looked at the top 25 most frequent error messages to identify the most common cause of build failure. The results indicated that only 10 percent of the error categories accounted for 90 percent of the broken builds, regardless of the language. Additionally, those errors where most commonly dependency related.

Insofar as these findings are generalizable to organizations outside of Google, the implications of this research suggest that dependency management is one of the most critical areas of concern for decreasing the amount of broken software builds. Potential actions could include reducing the dependencies for a given project, or developing assistive tools to help developers resolve dependency errors. Ideally, the goal should be to help prevent developers from submitting changes that contain dependency errors. In this study, the average resolution time was one to two additional builds. In this scenario, if we assume introducing a dependency-related bug requires two additional builds, the cost of such a bug is 3 times the elapsed build time in addition to the developer’s time required to resolve it.

Next Steps:

David Hubbell
Software Engineer
SPK and Associates

Latest White Papers

4 Strategies for Securing Container Deployments

4 Strategies for Securing Container Deployments

Utilizing containers can have many benefits for organizations in the IT realm. However, some teams experience pushback to adopting this technology due to security concerns. Let’s explore ways to ensure secure container deployments for your teams. What You Will Learn...

Related Resources

Accelerating Medical Software Compliance and Efficiency with SPK ACEs

Accelerating Medical Software Compliance and Efficiency with SPK ACEs

Compliance with regulatory standards is the number one priority for every medical manufacturer.  Ensuring pipelines are secure and compliant doesn’t just ensure safety, but it results in better quality products.  When a startup medical manufacturing company contacted...

Elevating Code Quality with SonarQube Cloud

Elevating Code Quality with SonarQube Cloud

Building secure, maintainable, and efficient software can be challenging. Achieving high-quality code to ensure these features requires a proactive approach to code analysis and quality control. SonarQube and SonarQube Cloud (previously named SonarCloud) provide...