> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/2025.5/quickstart-guide.md). # Quickstart guide A checklist for administrators setting up their initial installation of SonarQube Server 2025.5. By completing this guide you will: 1. [Download, install and configure SonarQube Server.](#install-the-server) 2. [Integrate SonarQube with your DevOps platform](#devops-platform-integration) 3. [Create or import a project](#onboard-your-projects) 4. [Configure CI analysis](#configure-your-ci-analysis) 5. [Integrate with SonarQube for IDE](#connect-with-sonarqube-for-ide) 6. [Review quality gates](#review-your-quality-gates) 1. Review pull/merge request analysis for failed quality gates. 2. Configure pull request decoration on your DevOps platform ## Before you begin Review the [Server host requirements](/sonarqube-server/2025.5/server-installation/server-host-requirements.md) and [Pre-installation steps](/sonarqube-server/2025.5/server-installation/pre-installation.md). This will help you establish a deployment plan (Zip, Docker, or Helm on Kubernetes) and then before you start [Installing database](/sonarqube-server/2025.5/server-installation/installing-the-database.md). Now you are ready to [download SonarQube Server](https://www.sonarsource.com/products/sonarqube/downloads/?_gl=1*1cb3ncb*_gcl_aw*R0NMLjE3NTY4MTY4NTAuQ2p3S0NBandxOXJGQmhBSUVpd0FHVkFaUDhpSnpMWFFYOFM0U1NYN1h6YUlEVkxqYWpaVzBENFoyaFZfNFlRMnU5ejVlZ2xkdE43dnd4b0M5ZFFRQXZEX0J3RQ..*_gcl_au*MTUyODQxMjM2OC4xNzU3OTQwNjA3LjIwNDk1NTUzMjIuMTc1OTkxNTc4Ny4xNzU5OTE1Nzg2*_ga*MzU0MTY0OTcwLjE3MjY2NzExODc.*_ga_9JZ0GZ5TC6*czE3NjA2MTUyNDkkbzEyMSRnMSR0MTc2MDYxNzkwOCRqNjAkbDAkaDA.). ## Install the server Choose your installation target: * [From ZIP file](/sonarqube-server/2025.5/server-installation/from-zip-file.md) * [From Docker image](/sonarqube-server/2025.5/server-installation/from-docker-image.md) * [Installing on Kubernetes or Openshift](/sonarqube-server/2025.5/server-installation/on-kubernetes-or-openshift.md) ## DevOps platform integration Next you will integrate SonarQube with your DevOps platforms: * [GitHub integration](/sonarqube-server/2025.5/devops-platform-integration/github-integration.md) * [Bitbucket integration](/sonarqube-server/2025.5/devops-platform-integration/bitbucket-integration.md) * [GitLab integration](/sonarqube-server/2025.5/devops-platform-integration/gitlab-integration.md) * [Azure DevOps integration](/sonarqube-server/2025.5/devops-platform-integration/azure-devops-integration.md) ## Onboard your projects You can [import projects from your DevOps platform](/sonarqube-server/2025.5/project-administration/creating-and-importing-projects.md#importing-repository) or [manually add local projects](/sonarqube-server/2025.5/project-administration/creating-and-importing-projects.md#creating-project-manually), see [Creating and importing projects](/sonarqube-server/2025.5/project-administration/creating-and-importing-projects.md) for more details including how to automate both methods using the [Web API](/sonarqube-server/2025.5/extension-guide/web-api.md). ## Configure your CI analysis Read [Project analysis setup](/sonarqube-server/2025.5/analyzing-source-code/overview.md) for guidance on setting up analysis for your imported projects * [Project analysis setup](/sonarqube-server/2025.5/analyzing-source-code/overview.md#sonarqube-server-is-integrated-with-your-devops-platform-ci-tool) * [Project analysis setup](/sonarqube-server/2025.5/analyzing-source-code/overview.md#the-sonarscanner-is-installed-on-the-ci-cd-host) ## Connect with SonarQube for IDE Have your developers install SonarQube for IDE to leverage the power of [Connected mode](/sonarqube-server/2025.5/user-guide/connected-mode.md) in their IDE. ## Review your quality gates The purpose of [quality gates](/sonarqube-server/2025.5/quality-standards-administration/managing-quality-gates.md) 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 the pull request analysis](/sonarqube-server/2025.5/analyzing-source-code/pull-request-analysis/setting-up-the-pull-request-analysis.md) analysis occurs when a pull request is opened and every time a change is pushed to the pull request branch. You can also configure [pull request decoration](/sonarqube-server/2025.5/analyzing-source-code/pull-request-analysis/introduction.md#decoration) to allow your developers to view the analysis from SonarQube server 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. ## Develop with Sonar Now that you have installed [SonarQube Server](/sonarqube-server/2025.5/readme.md#high-quality-code) with your DevOps platforms or CI pipeline, managers and tech leads can check out the [Security reports](/sonarqube-server/2025.5/user-guide/viewing-reports/security-reports.md) and [Portfolios](/sonarqube-server/2025.5/user-guide/viewing-reports/portfolios.md) features to begin monitoring the security and releasability of projects. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sonarsource.com/sonarqube-server/2025.5/quickstart-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.