/
Troubleshooting Agent Problems

Troubleshooting Agent Problems

Problem

A build was failing on the Checkout step:
Git fetch failed with exit code: 1
The detailed log showed the following:
![rejected] CORALv2.3.0 → CORALv2.3.0 (would clobber existing tag)

Solution

  1. This was happening after we had followed the procedures to remove a file from our repo's history (see this page).  This process updates the hashing algorithms (SHAs) of existing commits.
  2. It seems the build server was unable to perform a fetch of the repository.  The best solution in this case was to remove the existing repository from the build server and have it retrieve it from scratch.
  3. To do this we simply had to remove the existing "_work" directory on the build server.  On our build server (ncrws494) this lived at the following location:  D:\Software\vsts-agent-win-x64-2.149.2.
  4. After doing this we re-queued the build and it worked like a charm.



Related content

So You Want to Install and Use a Self-Hosted Azure DevOps Build and Release Agent
So You Want to Install and Use a Self-Hosted Azure DevOps Build and Release Agent
More like this
How-Tos And Fixes
How-Tos And Fixes
More like this
Troubleshooting Tips
Troubleshooting Tips
More like this
CAWIS MDM - SWIMN MDC
CAWIS MDM - SWIMN MDC
More like this
PLT Troubleshoot 2019-11-13
PLT Troubleshoot 2019-11-13
More like this