We've got a pipeline containing a shared library and multiple p4 checkout steps on different servers, with different p4 clients.
Polling perforce detects changes and starts build.
But if the build fails, the next polling step again changes are found, event though there are none and a new build is started, over and over again.
The Polling Log shows:
1129035 was the last change for our view and there are no new changes after this change. Any help on how to stop the Polling from thinking there are changes?