"rrajesh" wrote : This algorithm would work fine for build breakages. However one issue when we rollback the commits to a previous working version, we might lose the commits that were done after the build started; which would have ideally been included in the next build. | In that case, can we rollback to the previous working version and then apply the commits that were done after this build started? | In general the commits made after the build are invalid as they could rely on changes that need to be rolled back. The main issue is how are the rolled back changes identified and the responsible parties notified so that the breakage is fixed soon. "rrajesh" wrote : | For testsuite regressions, | * We need to get in place a notion of known failures, to actually track the regressions. | And, is rolling back the commits, a right option for testsuite regressions as well? | Not all tests are equal, which is why I only wanted to see this validated against integration tests where a failure means some contract usage is broken. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063274#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...