A checklist for administrators completing the initial setup of SonarQube Cloud.
By completing this guide you will:
Set up your SonarQube Cloud account
Set up your Organization
Upgrade to Enterprise
SSO via SAML
Review pull/merge request analysis for failed quality gates.
Configure pull request decoration on your DevOps platform
We use an organization-based structure that mirrors the structure on your chosen DevOps platforms.
Create an organization based on:
Consider upgrading to Enterprise so you can begin Setting up SSO.
Import repositories from your DevOps platform to create projects:
Set up analysis for your imported projects:
Now that you can review the main branch’s analysis on any of your imported projects.
Have your developers install SonarQube for IDE to leverage the power of SonarQube in their IDE.
The purpose of Quality gates is to tell you whether your code is good enough to be pushed to the next step:
For the main branch and other long-lived branches, the quality gate answers the question: "Can I release my code today?"
For pull requests (and short-lived branches), the quality gate answers the question: "Can I merge this pull request?"
By setting up Pull request analysis, you ensure pull requests are analyzed when they are opened and every time a change is pushed to the pull request branch. You can also configure pull request decoration to allow your developers to view the analysis from SonarQube Cloud directly on the PRs they submit.
By keeping an eye on the quality gates, the decision makers can quickly judge the status of code and decide what to do next.
Now that you have seen the benefits of using SonarQube Cloud with your DevOPs platforms, managers and tech leads can check out the security reports and portfolios features to begin monitoring the security and releasability of projects.
Last updated
Was this helpful?
Was this helpful?
