In reference to the patent: WO2013115797A1
This patent from Hewlett-Packard relates to automatically running a set of tests against a "plurality of code changes" to determine "the failed code change" by:
"removing at least one of the plurality of code changes from the subset each time the subset fails the set of tests"
The "management tool" claim reads like the use of a Continuous Integration tool, e.g. CruiseControl available since 2001.
The "decision engine" claim reads like the use of
git bisect run, available since at least 2007, possibly earlier.
The earliest article I can find on the web about the use of
run feature is "An introduction to the git bisect feature" by Nicolas Trangez, published in August 2007, an excerpt of which is:
No[w] the magic can start:
$ git-bisect run ./testcase.sh
d6514e8d9fe55827fe78d650548d948a4647fc50 is first bad commit
bisect run success
Exactly, like it should, it figured out commit 16 [...] broke our application.
In 2009, Atlassian's Justus Pendleton blogged about using
git bisect run.
Does anyone have examples of
git bisect run (or similar) used in an automated manner, perhaps as part of a continuous integration/delivery tool, prior to 2012?