Trade-offs in continuous integration: assurance, security, and flexibility

M Hilton, N Nelson, T Tunnell, D Marinov… - Proceedings of the 2017 …, 2017 - dl.acm.org
Proceedings of the 2017 11th Joint Meeting on Foundations of Software …, 2017dl.acm.org
Continuous integration (CI) systems automate the compilation, building, and testing of
software. Despite CI being a widely used activity 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, tool builders invest in the wrong
direction, and researchers miss opportunities for improving the practice of CI. We present a
qualitative study of the barriers and needs developers face when using CI. We conduct semi …
Continuous integration (CI) systems automate the compilation, building, and testing of software. Despite CI being a widely used activity 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, tool builders invest in the wrong direction, and researchers miss opportunities for improving the practice of CI. We present a qualitative study of the barriers and needs developers face when using CI. We conduct semi-structured interviews with developers from different industries and development scales. We triangulate our findings by running two surveys. We find that developers face trade-offs between speed and certainty (Assurance), between better access and information security (Security), and between more configuration options and greater ease of use (Flexi- bility). We present implications of these trade-offs for developers, tool builders, and researchers.
ACM Digital Library
以上显示的是最相近的搜索结果。 查看全部搜索结果