I’m seeing this in my logs; the “validate” button on the repo says it’s OK.I’ve not touched the config nor repo for ages (see https://github.com/jpluimers/DUnitX.git).
Repository Cannot get changes for repository DUnitX: Running git.exe with arguments “fetch --prune” failed with return code 128 and error output: “fatal: No remote repository specified. Please, specify either a URL or aremote name from which new revisions should be fetched.”
I’ve reset this repository (it had a .git/config file filled with nulls), but the building that was waiting for the repository to come up now is in an endless loop:
Not sure what happened there, but I cancelled the build and reset the dunitx repo and it seems to be building ok there again. I do notice that you still have the default workspace sync rules on that config, it’s copying a lot of files back to the server workspace… if you don’t need them then you can speed up your build process a lot by editing the workspace sync rules.
I already assumed this would solve itself when cancelling the build. But I think the built should have recovered itself and should have recognised that the repo was reset.