jswartwood
November 16, 2023, 8:00pm
2
It seems this is some odd CACHE issue with the way bamboo handles git caching.
The work-around fix described in the original post (Mostly) works: Sometimes you have to do a clean pull and clear the cache first.
There are many articles about it.
The odd thing is, only SonarScanner seems to be affected by this caching issue.
I wonder if it’s something SonarScanner needs to update to handle the caching situation?
Some links for reference:
https://jira.atlassian.com/browse/BAM-11930?focusedId=1795741&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1795741
We happened to encounter the same analysis warning after upgrading to 7.9.2 LTS.
Clone with a reference was detected. Some files will miss SCM information. This will affect features like auto-assignment of issues. Please configure your build to not clone using a local reference.
This was not an issue with 7.6, which we upgraded from. So this is definitely something that changed in 7.9.2.
We are currently using TeamCity 2018.1.3, and for us the fix was simply to add the build configuration p…
https://confluence.atlassian.com/bamkb/how-stored-git-caches-speed-up-builds-690848923.html