Is there a script that provides the equivalent to git-bisect for Perforce (p4)? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

开发者_JAVA技巧

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 7 years ago.

Improve this question

The git-bisect provides hooks to perform a binary search on revisions and figure out which change broke the design. Is there an equivalent script for Perforce? I did SO and Google searches with no luck.

Update Mar 1 2010: As Douglas Leeder correctly pointed out, this is easy with a linear history. However we do have multiple branches with merges going on between branches, so it isn't as trivial as it would be with linear history. Additionally building and testing the code takes some time (hours) so the automatic test would be nice to have it go without my coming back and for running overnight/on the weekened.

---

I don't think any explicit tool exists, I guess because syncing to a point in history in a centralized source control system is much easier, so no-one has felt the need for a tool.

Just sync back in history till you reach a point where the regression (that you are trying to trace) no longer happens, then sync to history between that point and HEAD, until you find the problem revision.