![]() SonarScanners running in Azure Pipelines jobs can automatically detect branches or pull requests being built, so you don't need to specifically pass them as parameters to the scanner.Īutomatic branch detection is only available when using Git. ![]() Setting up your projects this way also sets your project settings for pull request decoration.įor information on analyzing your projects with Azure Pipelines, see the Analyzing projects with Azure Pipelines section below. This token will be stored in SonarQube and can be revoked at anytime in Azure DevOps.Īfter saving your personal access token, you'll see a list of your Azure DevOps projects that you can set up to add them to SonarQube. Then, you'll be asked to provide a personal access token with Code (Read & Write) scope so SonarQube can access and list your Azure DevOps projects. You'll be asked for another personal access token for importing projects in the following section.Īdding a personal access token for importing repositoriesĪfter setting your global settings, you can add a project from Azure DevOps by clicking the Add project button in the upper-right corner of the Projects homepage and selecting Azure DevOps. This personal access token is used to report your Quality Gate status to your pull requests. See the Settings Encryption section of the Security page for more information. Administrators can encrypt this token at Administration > Configuration > Encryption. You need a personal access token from this account with the scope authorized for Code > Read & Write for the repositories that will be analyzed. We recommend using a dedicated Azure DevOps account with Administrator permissions. Personal Access Token – An Azure DevOps user account is used to decorate Pull Requests. If you are using Azure DevOps Services, provide your full Azure DevOps organization URL.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |