-
Bug
-
Resolution: Fixed
-
Medium
-
9.6.10, 10.2.1
-
None
-
Severity 3 - Minor
-
Issue Summary
When a repository has Shallow clones enabled and it is decided to revert the change back to "Full Clones" strategy and "Repository caching on Agents" is also enabled, further checkouts will remain shallowed.
This is reproducible on Data Center:
Steps to Reproduce
- Configure a Linked Repository with a "Shallow clone" strategy
- Run a build and validate the .git/shallow file is created
- Modify the Linked Repository settings and set it to "Full Clones" + "Repository caching on Agents"
- Run a build and validate if the .git/shallow file was removed
- Go to the Agent and run git log on the build working directory
Expected Results
- The .git/shallow should not exist
- The git log output should contain the complete repository history
Actual Results
- The .git/shallow is still present
- The git log output shows a shallow clone with only HEAD revisions
Workaround
Option 1:
- Modify the Linked Repository and disable "Repository caching on Agents"
- Run the build on the Agent (and any other affected agents)
- Set the Linked Repository with enabled "Repository caching on Agents"
Option 2:
- Clean all Agents working directories for that Plan, including .git contents
- Run a build normally
- mentioned in
-
Page Loading...