@mickaelcaro - Were in the progress of getting a new instance setup with that version however it may take a while to setup as we have to speak with other teams internally to get firewall rules applied etc…
Is there anything else in the meantime we can do to try do to troubleshoot further on the current version?
Hi @mickaelcaro - I’ve ran a build on the SonarQube version you mentioned and it still scans C# so it looks like the latest version of the sonar tfs extension isn’t compatible with the current version of our SonarQube instance. We’ll look to upgrade this.
Glad it works with that version. However i need to know on my side what is causing this. I’m running out of time these day to look at that but i’ll do my best.
Would you be able to send me a reproducer maybe ? That would be super helpful.
It would be good to find out what the issue is and potentially fix/provide a workaround for this SonarQube version as we haven’t upgraded our instance for a while so we’re not fully prepared at the moment to do this on our production instance.
Regarding sending you a reproducer - Can I just check you’re referring to this C++ developers now benefit from more efficient analysis and deeper Core Guidelines coverage ? - If so I’m assuming I should run this on our current version where the code fails to scan C#. How would I enable this , would just adding ’ sonar.cfamily.reproducer=true’ to a the variable within the tfs build be sufficient?
@mickaelcaro - I’m trying now to add that variable. Looks like I should be adding a path to the variable value as suggested here https://jira.sonarsource.com/browse/CPP-850 rather than =true so I’m trying that now however if the step doesn’t fail (which it doesn’t) will this fail to output this file ?
That didn’t seem to output any file when specifying a location on the variable. I’ll await your reply to advise before doing any other actions - Thanks
Hi @mickaelcaro - I wouldn’t be able to share our code with you I’m afraid (I think that’s the ask?). Do you have any projects internally that you can use ? I would have thought the issue would occur with any C# projects that use the version of SonarQube we are using (v6.7.4) and the latest tfs extension (v4.17.0).
I’m currently trying to investigate this issue (finally ! ) Can you please give me the version of the C# analyzer you have currently installed on your SQ 6.7 instance please ?
Thanks for that. I’ve just ran a build on a test instance using that version and it’s successfully scanned C# code now - I’ll upgrade the plugin to this version on our production instance.