| Currently we enable Sonar analysis on every single pipeline-based Search job, as soon as we find the Sonar credentials, which are global. This is annoying when we set up additional jobs, for example for forks, or for exceptional needs (such as testing Search with the next version of ORM). Let's provide a configuration option to enable/disable Sonar analysis. |