kirancodes.me
To Proof Maintenance & Beyond!
ICSE 2009

Safe-commit analysis to facilitate team software development

Jan Wloka, Barbara G. Ryder, Frank Tip, Xiaoxia Ren

Full textDOI 10.1109/icse.2009.5070549dblp

Abstract

Software development teams exchange source code in shared repositories. These repositories are kept consistent by having developers follow a commit policy, such as ldquoProgram edits can be committed only if all available tests succeed.rdquo Such policies may result in long intervals between commits, increasing the likelihood of duplicative development and merge conflicts. Furthermore, commit policies are generally not automatically enforceable. We present a program analysis to identify committable changes that can be released early, without causing failures of existing tests, even in the presence of failing tests in a developer's local workspace. The algorithm can support relaxed commit policies that allow early release of changes, reducing the potential for merge conflicts. In experiments using several versions of a non-trivial software system with failing tests, 3 newly enabled commit policies were shown to allow a significant percentage of changes to be committed.

BibTeX
@inproceedings{Wloka-al:ICSE09,
  author    = {Jan Wloka and
               Barbara G. Ryder and
               Frank Tip and
               Xiaoxia Ren},
  title     = {Safe-commit analysis to facilitate team software development},
  booktitle = {ICSE},
  pages     = {507--517},
  publisher = {{IEEE}},
  year      = {2009},
}

Related papers