Dear community,
We’re excited to announce SonarQube CLI v1.9.0, a release that makes sonar integrate work globally across all your projects, introduces sonar import in beta, and delivers quality-of-life improvements across authentication, output formatting, and CI onboarding — plus several bug fixes and security hardening items.
What’s new
Integrations now configure globally
sonar integrate has been redesigned to configure integrations once, globally, instead of per project. This unifies configuration, cuts down on duplication, and simplifies management across multiple repos.
- On first run of v1.9.0, an automatic migration cleans up existing project-level integration artifacts and moves them to the global configuration.
- If your project key can’t be auto-discovered during migration, run
sonar link <project-key>to connect it to SonarQube manually.
Import repositories with sonar import (Open Beta)
The new sonar import command lets you import repositories from a connected DevOps platform straight into SonarQube.
Smaller improvements
sonar update --statusis now a propersonar update statussubcommand (consistent withsonar auth status/sonar system status), and supports--formatfor JSON output.sonar auth login --with-tokenlets you pass a token directly for non-interactive authentication flows.- All data commands now accept a uniform
--formatflag for JSON output. sonar admin onboard-ci gitlabaccepts a--job-template <file>flag so you can inject your own YAML job definition instead of the default template.sonar auth statusnow clearly flags when your token has no membership for the configured organization, instead of silently showingConnectedwhile features like Vortex stay unavailable.
You can find more information about this release here.
Run the sonar update command to get the latest SonarQube CLI version and enjoy these new capabilities!
Happy coding,
Farah