Attempting to use the non-compliant code example from the docs to test rules in our pipeline. We have committed the code example to test success and fails. We are expecting the example to fail since it includes “senstive information”.
What we have tried
Renaming project names (removed “test” from the project and files. Do projects get skipped when “test” is in the name)
Thank you for reporting this false negative. After having a look, it seems that the rule behaves a bit too conservatively in some cases, which also affects the non-compliant code example.
When it’s fixed, you’ll need to upgrade to the next version of SonarQube that’s released. The ticket is currently in progress, so that means adopting SonarQube 10.4 when it comes out.
I was just curious if anyone knows the expected release date for SonarQube 10.4? I seen the ticket has been closed and just wanted an idea of when we can expect to see it and keep an eye out for it.