Continuous Integration (CI) Needs and Wishes for Developers of Proprietary Code Public Deposited

http://ir.library.oregonstate.edu/concern/technical_reports/2z10wr50b

Descriptions

Attribute NameValues
Creator
Abstract or Summary
  • Continuous integration (CI) systems automate the compilation, building, and testing of software. Despite CI being one of the most widely used processes in software engineering, we do not know what motivates developers to use CI, and what barriers and unmet needs they face. Without such knowledge developers make easily avoidable errors, managers reduce the productivity of developers by making misinformed decisions, tool builders invest in the wrong direction, and researchers miss many opportunities for improving the software engineering practice. Given the large fraction of proprietary code development, understanding how proprietary developers are using CI is vital to improving it. We present the first study of how CI is used in the proprietary development of software. We conduct 16 semi-structured interviews with developers from different industries and development scale. We generalize these findings by surveying 523 developers from all over the world. We find that 78% of developers feel more productive when using CI, and 85% think that using CI causes developers to give more value to automated testing. However, unlike open-source developers, many proprietary developers want to use CI but are not allowed to do so. 50% of developers have problems troubleshooting CI builds, and more than half of developers want easier configurations for CI tools and services.
Resource Type
Date Available
Date Issued
Series
Keyword
Rights Statement
Funding Statement (additional comments about funding)
Publisher
Peer Reviewed
Language
Replaces
Additional Information
  • description.provenance : Submitted by Michael Hilton (hiltonm@onid.orst.edu) on 2016-09-21T22:21:00Z No. of bitstreams: 1 CI_Interview_Paper_OSU_TechReport.pdf: 259963 bytes, checksum: b34f8efe6bfbf35cf8a190b66499f528 (MD5)
  • description.provenance : Made available in DSpace on 2016-09-27T20:27:29Z (GMT). No. of bitstreams: 1 CI_Interview_Paper_OSU_TechReport.pdf: 259963 bytes, checksum: b34f8efe6bfbf35cf8a190b66499f528 (MD5)
  • description.provenance : Approved for entry into archive by Steven Van Tuyl(steve.vantuyl@oregonstate.edu) on 2016-09-27T20:27:29Z (GMT) No. of bitstreams: 1 CI_Interview_Paper_OSU_TechReport.pdf: 259963 bytes, checksum: b34f8efe6bfbf35cf8a190b66499f528 (MD5)

Relationships

Parents:

This work has no parents.

Last modified

Downloadable Content

Download PDF

Items