Survey on how Developers React to CI Build Failures

Among the benefits provided by Continuous Integration (CI), increased team productivity and integration frequency are perceived as the main advantages. However, changes that contain defects or that suffer from a poor-quality can lead to build failures that stop a team from delivering. The recent Report on the State of DevOps states: “When failures occur, it can be difficult to understand what caused the problem” and previous work found that developers spend on average one hour to fix build breaks!

In our group at the University of Zurich (Switzerland), we are developing new strategies to provide developers with the right assistance to solve build failures faster and more efficiently. To achieve this, we first need to understand the state of practice from real developers and we would like to learn about your personal experience with build failures in this survey.

We would really appreciate if you could find the time to fill out the following survey to help us in our research.

Filling out the survey will take you about 7 minutes. Please note that participating in the questionnaire is completely anonymous, but we will publish the anonymized answers as part of a scientific publication.

If you have any questions about the questionnaire or our research, please do not hesitate to contact us.

Image from “Arduino Jenkins CI build monitor using car lights”, Gordons Garage, YouTube, 2016.

Originally published at http://sealuzh.wordpress.com on February 6, 2019.