Non-TFS projects are broken with "Missing configuration for CollectionUri" about sonar-scm-tfvc HOT 13 CLOSED

We are also seeing this issue with 8.3-enterprise. It's definitely throwing a new exception and keeping us from upgrading to the 2.3+ version of this plugin. We don't want to add the uri manually to each job. This is happening for Azure DevOps git repos for us.

from sonar-scm-tfvc.

I'm sorry for the strong delay. I'm wondering why I never realized all your comments.
I myself am using the plugin 2.3.0 in my company without any problem, so I did had contiguous view on this repository.

Yes, this could be an regression. I'll have a look on the changes soon.
Maybe you have an idea to resolve the initial issue together with this regression.

from sonar-scm-tfvc.

Would you like to test the version build from the PR?
https://ci.appveyor.com/project/lg2de/sonar-scm-tfvc/builds/38577462/artifacts

Please note that this is a testing build only!

from sonar-scm-tfvc.

We are also having this issue. We had to uninstall the plugin.

from sonar-scm-tfvc.

Same problem on SonarQube 7.9.1 (plugin version 2.3.0 build 73): GIT repo are recognized as TFVC!

from sonar-scm-tfvc.

We are attempting to add this plugin as well for a project that uses TFVC and it is causing our other scans to fail which are all Git repos.

from sonar-scm-tfvc.

We also have this problem on both 7.9 and 8.6. We had to uninstall the plugin.

from sonar-scm-tfvc.

Please update your Azure Devops URI alone, without any pat token and enable the diable scm sensor toggle

from sonar-scm-tfvc.

Hi @lg2de, thanks for the reply. It seems like this issue only impacts non-TFVC repositories. It would be nice to be able to easily have projects from both TFVC and other repositories in tandem without having to configure anything extra for the non-TFVC repos. I wonder if a better solution to #22 would be to just have clear logging about the impact of an unconfigured URI (looks like these statements were already added in #53) rather than triggering a hard failure.

from sonar-scm-tfvc.

We unfortunately don't currently have an instance suitable for testing :( the changes seem like they're likely to fix it though. Maybe somebody else would be able to pick up the torch? Otherwise, I can see if I can find bandwidth to spin up a test instance sometime this week or next.

from sonar-scm-tfvc.

We can't initially test it with TFVC but we can test whether or not it breaks Github. Will test tomorrow (4/8).

from sonar-scm-tfvc.

We tested this version of the plugin with our Github-based builds and the scans completed. We received a warning about no TFVC but it did not fail the scan which was the original issue. Working with our TFS devs to get them to scan with the plugin.

from sonar-scm-tfvc.

Will be fixed with version 2.3.1.

from sonar-scm-tfvc.