Modeling continuous integration practice differences in industry software development

Ståhl, Daniel; Bosch, Jan

doi:10.1016/j.jss.2013.08.032

Cited by 184 publications

(102 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Continuous integration as an agile practice (Beck et al 2001) enables early identification of integration issues as well as increases the developers' productivity and release frequency (Ståhl and Bosch 2014). With this reasoning, as reported elsewhere (Linåker et al 2015), we deem that the product innovations captured in Jenkins and Gerrit transfer on as process innovation to Sony Mobile's product development.…”

Section: Innovation Outcomesmentioning

confidence: 63%

Open innovation using open source tools: a case study at Sony Mobile

et al. 2017

View full text Add to dashboard Cite

Despite growing interest of Open Innovation (OI) in Software Engineering (SE), little is known about what triggers software organizations to adopt it and how this affects SE practices. OI can be realized in numerous of ways, including Open Source Software (OSS) involvement. Outcomes from OI are not restricted to product innovation but also include process innovation, e.g. improved SE practices and methods. This study explores the involvement of a software organization (Sony Mobile) in OSS communities from an OI perspective and what SE practices (requirements engineering and testing) have been adapted in relation to OI. It also highlights the innovative outcomes resulting from OI. An exploratory embedded case study investigates how Sony Mobile use and contribute to Jenkins and Gerrit; the two central OSS tools in their continuous integration tool chain. Quantitative analysis was performed on change log data from source code repositories in order to identify the top contributors and triangulated with the results from five semi-structured interviews to explore the nature of the commits. The findings of the case study include five major themes: i) The process of opening up towards the tool communities correlates in time with a general adoption of OSS in the organization. ii) Assets not seen as competitive advantage nor a source of revenue are made open to OSS communities, and gradually, the organization turns more open. iii) The requirements engineering process towards the community is informal and based on engagement. iv) The need for systematic and automated testing is still in its infancy, but the needs are identified. v) The innovation outcomes included free features and maintenance, and were believed to increase speed and quality in development. Adopting OI was a result of a paradigm shift of moving from Windows to Linux. This shift enabled Sony Mobile to utilize the Jenkins and Gerrit communities to make their internal development process better for its software developers and testers.

show abstract

Section: Innovation Outcomesmentioning

confidence: 63%

Open innovation using open source tools: a case study at Sony Mobile

et al. 2017

View full text Add to dashboard Cite

show abstract

“…In their 2014 systematic review, Ståhl and Bosch provided the most recent overview over CI practices and how they differ in various settings of industrial software development [17]. Of particular interest to us is their analysis of what is considered a failure in a CI build.…”

Section: Related Workmentioning

confidence: 99%

Oops, my tests broke the build: An analysis of Travis CI builds with GitHub

Beller

Gousios

Zaidman

2016

Preprint

View full text Add to dashboard Cite

Continuous Integration (CI) has become a best practice of modern software development.At present, we have a shortfall of insight into the testing practices that are common in CIbased software development. In particular, we seek quantifiable evidence on how central testing really is in CI, how strongly the project language influences testing, whether different integration environments are valuable and if testing on the CI can serve as a surrogate to local testing in the IDE. In an analysis of 2,640,825 Java and Ruby builds on Travis CI, we find that testing is the single most important reason why builds fail.Moreover, the programming language has a strong influence on both the number of executed tests, their test run time and proneness to fail. The use of multiple integration environments leads to 10% more failures being caught at build time. However, testing in the CI does not seem to be a good surrogate for running tests in the IDE.

show abstract

“…The broader use context envisaged for our tools is Service Centred Continuous Engineering [5], which extends the continuous design and continuous deployment of [105] to a continuous lifecycle support paradigm where users co-define and co-manage the design and the evolution of deployed systems. This approach requires the coherent support of different levels of expertise and different concerns among the cooperating participants, and thus requires adaptability also of the technological means, including the design environment (like the jABC) itself.…”

Section: Cinco: Generating Tailored Frameworkmentioning

confidence: 99%

Scientific workflows with the jABC framework

Lamprecht

Steffen

Margaria

2016

Int J Softw Tools Technol Transfer

View full text Add to dashboard Cite

The jABC is a framework for process modelling and execution according to the XMDD (eXtreme Model-Driven Design) paradigm, which advocates the rigorous use of user-level models in the software development process and software life cycle. We have used the jABC in the domain of scientific workflows for more than a decade now -an occasion to look back and take stock of our experiences in the field. On the one hand, we discuss results from the analysis of a sample of nearly 100 scientific workflow applications that have been implemented with the jABC. On the other hand, we reflect on our experiences and observations regarding the workflow development process with the framework. We then derive and discuss ongoing further developments and future perspectives for the framework, all with an emphasis on simplicity for end-users through increased domain specificity. Concretely, we describe how the use of the PROPHETS synthesis plugin can enable a semanticsbased simplification of the workflow design process, how with the jABC4 and DyWA frameworks more attention is paid to the ease of data management, and how the Cinco SCCE Meta Tooling Suite can be used to generate tailored workflow management tools.

show abstract

Modeling continuous integration practice differences in industry software development

Cited by 184 publications

References 4 publications

Open innovation using open source tools: a case study at Sony Mobile

Open innovation using open source tools: a case study at Sony Mobile

Oops, my tests broke the build: An analysis of Travis CI builds with GitHub

Scientific workflows with the jABC framework

Contact Info

Product

Resources

About