|
It sounds like machines A and B tried to update the global macros file simultaneously. If they truly do need to share updates to that file, it would probably be best to prevent both build boxes from performing a build at the same time.
One way to do that would be to exit (or wait in a loop) at the beginning of the build if a signal macro existed, creating that global macro next if it doesn't exist, and delete it at the end of the build (on success or failure).
If the macro changes don't actually have to be shared, another option may be to copy the global macros file locally and load the local copy (so changes during the build are saved there) at the start of the build.
|