If perforce files end up open for edit, syncs dont work but Bamboo still builds

If for some reason files in the working directory for a Perforce build have their status change to read/write, when you do a sync the changes will not overwrite the open files. You can end up with some changes from a change set and not others. Bamboo does not recognise this error and assumes the sync completed successfully, and continues to run the build (which may ultimately fail because the source is not all there).

Example error Message received from Perforce:

//bambooDev/successBuild/file with spaces.txt#74 - is opened and not being changed
... //bambooDev/successBuild/file with spaces.txt - must resolve #74 before submitting

We essentially just need to put in a check for this particular error message and throw a Repository Exception to prevent the build from occurring.