+++ /dev/null
----
-title: AutoScan Beta Feature
-nav: AutoScan
-url: /autoscan/
----
-
-SonarCloud can autonomously scan your code, by simply reading it from your repository! We call that AutoScan.
-
-[[info]]
-| This is currently a Beta feature, with a limited scope and some caveats. Those limitations will be removed along the way.
-
-
-## Prerequisites
-
-* The first version of this Beta feature works only for GitHub repositories.
-* The automatic analysis can be activated only on projects which are bound to their remote repository. This implies that the the project was set up through the SonarCloud web interface by selecting a repository (i.e. not "manually").
-
-## What to expect
-
-Once activated, SonarCloud will automatically analyze:
-* the default branch of the repository
-* the pull requests (PR)
-
-It will take care of doing it whenever you push on your repository.
-
-The following languages are currently supported:
-* ABAP
-* Apex
-* CSS
-* Flex
-* Go
-* HTML
-* JS
-* Kotlin
-* PHP
-* Python
-* Ruby
-* Scala
-* Swift
-* TypeScript
-* TSQL
-* XML
-
-## How to activate the feature?
-
-To enable the automatic analysis, you need to add a `.sonarcloud.properties` file in your repository.
-
-If you're starting from scratch:
-
-1. Do the [setup for your project](/#sonarcloud#/projects/create) (from the `+ > Analyze new project` top right menu)
- *  Remember that your project must absolutely be created by selecting a GitHub repository - otherwise it won't work.
-1. Once the setup is done on SonarCloud, you end up on the project home page which shows a tutorial. Ignore it and simply add a `.sonarcloud.properties` file in the base directory of your default branch or on a PR.
-1. After a while, the analysis results will be visible in SonarCloud (and your PR will be annotated with comments if you pushed the file on a PR)
-
-Here are the supported optional settings for the `.sonarcloud.properties` file:
-```
-# Path to sources
-#sonar.sources=.
-#sonar.exclusions=
-#sonar.inclusions=
-
-# Path to tests
-#sonar.tests=
-#sonar.test.exclusions=
-#sonar.test.inclusions=
-
-# Source encoding
-#sonar.sourceEncoding=UTF-8
-
-# Exclusions for copy-paste detection
-#sonar.cpd.exclusions=
-```
-
-Note that you can just push an empty `.sonarcloud.properties` file, this will work fine. In this case, every file in the repository will be considered as a source file.
-
-## Current limitations/caveats
-
-* There is no visual feedback (yet) in the UI when SonarCloud runs an analysis.
-* A consequence of the previous point is that if - for any reason, SonarCloud fails to successfully run the analysis, nothing will be displayed. In that case, just come on [the forum](https://community.sonarsource.com/tags/c/help/sc/autoscan) and ask a question, we'll monitor that closely.
-* Code coverage information is not supported
-* Import of external rule engine reports is not supported
-
-## Noteworthy
-
-* This Beta feature works for any project - public or private.
-* It can be activated with no extra cost.
-* Sources are cloned only during the analysis, and only when the `.sonarcloud.properties` file exists (i.e. when the feature is activated). The cloned repository is fully deleted at the end of the analysis, and SonarCloud does not keep a copy of it.
-* Non supported languages (Java, C#, VB.NET, C/C++, ObjectiveC) are not analyzed at all.
-
-## How to give feedback?
-
-Create a new thread on the forum, under ["Get Help > SonarCloud"](https://community.sonarsource.com/tags/c/help/sc/autoscan), with the "autoscan" tag.
-
-We'd love to hear your feedback about this new upcoming feature, may it be about bugs, improvements, or anything you want to share with us!
+++ /dev/null
----
-title: Analyze your repository with Azure Pipelines
-nav: With Azure Pipelines
-url: /integrations/bitbucketcloud/azure-pipelines/
----
-
-If you are analyzing .NET applications and want to benefit from the Azure DevOps / Pipelines experience and features, you have the possibility to setup a build pipeline, targeting your Bitbucket Cloud repository, and connected to SonarCloud.
-
-## Analyzing branches
-
-Please be advised that the team where the Bitbucket Cloud repository is has to be bound to your SonarCloud organization in order to get this work.
-
-1. Install the SonarCloud extension for Azure DevOps in your Azure DevOps organization : [SonarCloud extension](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarcloud). You can have a look a [this chapter](https://docs.microsoft.com/en-us/labs/devops/sonarcloudlab/index?tutorial-step=1) of the global tutorial for Azure DevOps.
-
-2. Configure a new build pipeline (YAML or classic editor), targeting your Bitbucket Cloud repository. You will have to create a new service connection to that repository.
-
-3. Configure the Prepare SonarCloud configuration task just the way you will do for a regular Azure Git Repository.
-
-4. Go to the triggers tab of the pipeline configuration, click on the repository below `Continuous Integration` then click on `Enable continuous integration`, add a new branch filter with following configuration :
- * Type : Include
- * Branch specification : master
-
-Want to see how it is working ? Have a look at our [sample .NET project](https://bitbucket.org/sonarsource/sample-dotnet-project-azuredevops)
-
-## Analyzing pull requests
-
-Pre-requisites :
-
-* Follow the initiation steps of Analyzing branches with Azure pipelines above.
-* Version 1.6.4+ of the Azure DevOps extension is needed.
-
-As for branches, you can trigger an analysis for Pull requests with an Azure DevOps pipeline and get your PR decorated.
-
-1. On the Azure pipeline that will be used, click on the `Triggers` tab, then click on the repository below `Pull request validation`
-
-2. Click on `Enable pull request validation` then configure the proper branch filters.
+++ /dev/null
----
-title: Analyze your repository with Bitbucket Pipelines
-nav: With Bitbucket Pipelines
-url: /integrations/bitbucketcloud/bitbucket-pipelines/
----
-
-## Analyzing branches
-
-Once your project is created and initiated from the repository you selected:
-
-1. Generate a token to allow to publish analysis from Bitbucket Pipelines. To generate a token, follow the first step of the tutorial on the dashboard of the project, or go to your user security page.
-
-2. On Bitbucket Cloud, go to the "Settings > Pipelines > Account variables" page of your team, and add a new SONAR_TOKEN variable that contains the value of the SonarCloud token (something like `9ad01c85336b265406fa6554a9a681a4b281135f`).
- * **Make sure that you click on the "Lock" icon to encrypt and hide this token.**
-
-3. Edit the `bitbucket-pipelines.yml` file of your repository to trigger the SonarCloud analysis.
-
-Once those changes are pushed, Pipelines will automatically trigger analyses on the repository.
-
-You can see our multiple sample projects to see how it is working :
-
- * [Built with Gradle](https://bitbucket.org/sonarsource/sample-gradle-project)
- * [Built with Maven](https://bitbucket.org/sonarsource/sample-maven-project)
- * [Javascript project](https://bitbucket.org/sonarsource/sample-nodejs-project)
-
-If you target a .NET application, see a [sample .NET project](https://bitbucket.org/sonarsource/sample-dotnet-project-azuredevops) built with Azure Pipelines
-
-## Analyzing pull requests
-
-In order to trigger SonarCloud analysis on each pull request update, you have to supply the same command in the `pull-requests` section of `bitbucket-pipelines.yml` (check [Configure bitbucket-pipelines.yml](https://confluence.atlassian.com/bitbucket/configure-bitbucket-pipelines-yml-792298910.html#Configurebitbucket-pipelines.yml-ci_pull-requests) for more details about that section). Here is a sample configuration:
-```
-pipelines:
- ...
- pull-requests:
- feature/*:
- - step:
- script:
- - mvn sonar:sonar
- ...
-```
-
-In order to avoid duplication between the different sections of your `bitbucket-pipelines.yml`, you can use [yaml anchors and aliases](https://confluence.atlassian.com/bitbucket/yaml-anchors-960154027.html).
+++ /dev/null
----
-title: Get started with Bitbucket Cloud
-nav: Bitbucket Cloud
-url: /integrations/bitbucketcloud/
----
-
-## Sign up and set up your first project
-1. On the [login page](/#sonarcloud#/sessions/new), click on the "Log in with Bitbucket" button and connect to SonarCloud using your Bitbucket Cloud account.
-2. Click on "Analyze your code" and follow the path to set up a first project
-3. You will be asked to install the SonarCould application on your team or user account, which will allow you to
- choose which repositories you want to analyze.
-
-## Analyzing your repository
-
-* [With Bitbucket Pipelines](/integrations/bitbucketcloud/bitbucket-pipelines/)
-* [With Azure Pipelines](/integrations/bitbucketcloud/azure-pipelines/), if you analyze .NET applications and want to benefit from Azure DevOps features.
-
-## Quality widget
-
-SonarCloud can provide a widget that shows the current quality metrics of your project directly on the repository's Overview page on Bitbucket Cloud.
-
-If you want to see this widget, you can go to the "Settings > SonarCloud" page of your repository and check "Show repository overview widget".
-
-## FAQ
-
-**Do you have sample projects on Bitbucket Cloud?**
-You can take a look at these various projects: [Sample projects analyzed on SonarCloud](https://bitbucket.org/account/user/sonarsource/projects/SAMPLES)
-
-**I don't see the widget with quality information whereas I configured everything**
-Make sure that your browser is not using some extensions like AdBlocks. They tend to break the integration of third-party applications in BitBucket Cloud.
-
-## Upcoming features and improvements
-
-There are various areas in which you can expect new features and improvements:
-
-* Pull request decoration with inline comments to show the issues within the PR
-* Better and easier team onboarding
-* Automatic analysis (i.e. no need to configure anything from Pipelines)
+++ /dev/null
----
-title: Get started with GitHub.com
-nav: GitHub
-url: /integrations/github/
----
-
-## Sign up and set up your first project
-
-1. On the [login page](/#sonarcloud#/sessions/new), click on the "Log in with GitHub" button and connect to SonarCloud using your GitHub account.
-2. Click on "Analyze your code" and follow the path to set up a first project
-3. You will be asked to install the SonarCould application on your organization, which will allow you to choose which
- repository you want to analyze.
-
-## Trigger analyses
-
-For GitHub repositories, there are 2 ways to have your code analyzed:
-
-### ... with AutoScan
-
-With AutoScan, SonarCloud will autonomously pull your code and scan your default branch and your pull requests.
-Please read the ["AutoScan Beta Feature"](/autoscan/) documentation page to get the details.
-
-[[warning]]
-| This is currently a Beta feature which does not work for all languages and comes with limitations.
-
-### ... using your CI service
-
-If AutoScan does not make sense yet for your repository, you need to configure your CI service to trigger the analysis.
-
-**If you are using Travis CI**, the SonarCloud Travis Add-on will make it easier to activate analyses:
-
-* Read the [guide to integrate with Travis CI](https://docs.travis-ci.com/user/sonarcloud/)
-* Check out the [various sample projects](https://github.com/SonarSource/sonarcloud_examples) (Java, TypeScript, C/C++, Go, ... etc) that are analyzed on SonarCloud on a frequent basis
-
-**If you are using another CI service**, you will need to read:
-
-* the ["Analyzing Source Code" overview page](/analysis/overview/)
-* the ["Branches" overview page](/branches/overview/)
-* the ["Pull Request Analysis" page](/analysis/pull-request/)
-
-Here is an example of configuration for pull requests when you are not on Travis CI and you need to configure your CI jobs:
-```
-sonar.pullrequest.base=main
-sonar.pullrequest.branch=feature/my-new-feature
-sonar.pullrequest.key=5
-sonar.pullrequest.provider=GitHub
-sonar.pullrequest.github.repository=my-company/my-repo
-```
-
-[[info]]
-| Pull request decoration works only if [the SonarCloud application](https://github.com/apps/sonarcloud) is installed on your GitHub organization(s) and configured to have acccess to the repositories.
+++ /dev/null
----
-title: Get started with Azure DevOps Services
-nav: Azure DevOps Services
-url: /integrations/vsts/
----
-
-[[info]]
-| This page is about Azure DevOps Services, formerly known as VSTS.
-
-You can connect to SonarCloud using your Azure DevOps account. On the [login page](/#sonarcloud#/sessions/new), just click on the "Log in with Azure DevOps" button.
-
-[[warning]]
-| Only work and school Azure DevOps accounts are authorized to login on SonarCloud.
-
-## Install the SonarCloud Azure DevOps extension
-
-The SonarCloud Azure DevOps extension brings everything you need to have your projects analyzed on SonarCloud
-very quickly:
-* Integration with the Build definitions to easily trigger the analysis
-* Pull request decoration to get quick feedback on the code changes
-* Widget to have the overview quality of your projects inside Azure DevOps dashboards
-
-Install [SonarCloud extension for Azure DevOps](https://marketplace.visualstudio.com/items?itemName=SonarSource.sonarcloud)by clicking on the "Get it free" button.
-
-Then follow the comprehensive [Microsoft lab on how to integrate Azure DevOps with SonarCloud](https://aka.ms/sonarcloudlab).
-
-## Quality Gate Status widget
-
-You can monitor the Quality Gate status of your projects directly in your Azure DevOps dashboard. Follow these simple steps to configure your widget:
-
-1. Once the Azure DevOps extension is installed and your project has been successfully analyzed, go to one of your Azure DevOps dashboards (or create one). Click on the pen icon in the bottom right corner of the screen, and then on the "+" icon to add a widget.
-
-2. In the list of widgets, select the "Code Quality" one and then click on the "Add" button. An empty widget is added to your dashboard.
-
-3. You can then click on the widget's cogwheel icon to configure it.
-
- * **For public projects:** you can simply select your project from the dropdown. A searchbar inside the dropdown will help you find it easily. Just select it and click on the "Save" button.
-
- * **For private projects:** you'll have to log in using the links provided under the dropdown. Once logged in, your private projects will appear in the dropdown. Select the one you are interested in, and click on "Save".
-
-## FAQ
-
-1. Which kind of analysis scenario are supported for .Net projects ?
-
- * Using Sonar Scanner for MSBuild, you can build multiple .Net projects / solutions between the "Prepare Analysis on SonarCloud" and "Run Analysis" tasks. You will have full support of Issues and Code Coverage on both branches and PR Analysis. Other kind of scenarios are not yet supported.
\ No newline at end of file
+++ /dev/null
----
-title: Organizations
-url: /organizations/overview/
----
-
-## Overview
-
-An organization is a space where a team or a whole company can collaborate across many projects.
-
-An organization consists of:
-
-- Projects, on which users collaborate
-- [Members](/organizations/manage-team/), who can have different permissions on the projects
-- [Quality Profiles](/instance-administration/quality-profiles/) and [Quality Gates](/user-guide/quality-gates/), which can be customized and shared accross projects
-
-Organizations can be on:
-
-- **Free plan**. This is the default plan. Every project in an organization on the free plan is public.
-- **Paid plan**. This plan unlocks the ability to have private projects. Go to the "Billing" page of your organization to upgrade it to the paid plan.
-
-Depending on which plan the organization is in, its [visibility](/organizations/organization-visibility/) will change.
-
-You can create organizations from the top right menu "+ > Create new organization"
-
-## FAQ
-
-### How to bind an existing organization to GitHub or Bitbucket Cloud?
-
-You might notice the following warning message on your pull requests inside SonarCloud:
-
- The SonarCloud GitHub application is installed on your GitHub organization, but the
- SonarCloud organization is not bound to it. Please read "How to bind an existing
- organization?" section in the "Organizations" documentation page to fix your setup.
-
-This means that your SonarCloud organization is not bound to GitHub or Bitbucket Cloud whereas you had already installed the SonarCloud application (probably to annotate pull requests). To fix your setup, here are the steps to follow.
-
-**For GitHub:**
-
-1. Click your profile picture in the top right menu and select the organization.
-2. In the organization menu, click "Administration > Organization settings"
-3. Click on "Choose an organization on GitHub".
-4. On GitHub page, you should see a list of organization you are admin of. The organization you want to bind is marked as already configured. Click on it.
-5. Click on "Uninstall" at the bottom of the page.
-6. Go back to SonarCloud, to the settings page of your organization, and click on "Choose an organization on GitHub" again. The organization you want to bind should not be marked as configured anymore. Click on it, and then on "Install". After the installation, you will be redirected to SonarCloud.
-7. You are all set! You should see a GitHub icon close to the name of your organization at the top of the page.
-
-**For Bitbucket Cloud:**
-
-1. Click your profile picture in the top right menu and select the organization.
-2. In the organization menu, click "Administration > Organization settings"
-3. Click on "Choose a team on Bitbucket".
-4. On Bitbucket Cloud page, select the name of the team you want to bind and click on "Grant access". You will then be redirected to SonarCloud.
- [[warning]]
- | If you get a 405 error page from Bitbucket Cloud at this stage, this means that you did not approve a recent scope change - for which you should have received an email from Bitbucket Cloud. The easiest way to get around this is to uninstall the SonarCloud application in your Bitbucket Cloud "Install apps" settings, and reinstall it.
-5. You are all set! You should see a Bitbucket Cloud icon close to the name of your organization at the top of the page.
-
-### How to transfer ownership of an organization?
-
-You may want to transfer ownership of you organization when you want to delete your account, or when you are leaving a team or company.
-You can manage your organization members permissions in: "Administration > Permissions" and [grant "Administer Organization" permission](/organizations/manage-team/#granting-permissions) to another member.
-
-### How to delete an organization?
-
-You can delete your organization in: "Administration > Organization Settings > Delete Organization".
+++ /dev/null
----
-title: Manage a Team
-url: /organizations/manage-team/
----
-
-Members can collaborate on the projects in the organizations to which they belong. Depending on their permisssions within the organization, members can:
-* Analyze projects
-* Manage project settings (permissions, visibility, Quality Profiles, ...)
-* Update issues
-* Manage quality gates and Quality Profiles
-* Administer the organization itself
-
-Members are managed on the "Members" page of the organization. Only organization administrators can manage members.
-
-## Managing Members Manually
-Members are managed manually when synchronization is not available (for Bitbucket Cloud or Azure Devops for example) or when synchronization is deactivated.
-
-### Adding Members
-You can add members to an organization using the "Add a member" button. Administrators can search manually for SonarCloud users and add them as members.
-
-## Managing Members in GitHub
-For organizations that are bound to GitHub, members can be synchronized with GitHub organizations or managed manually.
-
-Note that in all cases, members should have a SonarCloud account before being synchronized with GitHub or added manually.
-
-### Synchronizing Members with your GitHub Organization
-When [importing](/organizations/overview/) a GitHub organization into SonarCloud, members are automatically synchronized with your GitHub organization.
-This means that each member of your GitHub organization who has a SonarCloud account will be automatically added to the SonarCloud organization,
-and will have direct access in SonarCloud to the organizations they've been added to.
-
-You can synchronize a bound organization with manually managed members using the "Configure synchronization" button.
-During synchronization, members of the SonarCloud organization who are not part of the GitHub organization are removed from the SonarCloud
-organization and members of the GitHub organization who are not members of the SonarCloud organization are added to the SonarCloud organization.
-
-After creating an organization or activating synchronization, SonarCloud users that are added or removed from the GitHub organization are automatically added or removed from
-the SonarCloud organization. It's not possible to manually add or remove a member when synchronization is activated.
-
-Permissions are not synchronized and must be managed manually (see below).
-
-### Deactivating Member Synchronization
-You can deactivate member synchronization using the "Configure synchronization" button.
-When you deactivate member synchronization, no members will be added or removed automatically.
-After deactivating synchronization, members will be managed manually.
-
-
-## Granting permissions
-Once users are added or synchronized, organization administrators can grant them permissions to perform specific operations in the organization. It is up to the
-administrators to make sure each member gets the relevant permissions.
-
-To avoid having to manage individual permissions at a project level, organization admins can create groups to manage permissions
-and add new users to those groups on the "Members" page.
-
-## Future evolutions
-Future versions of SonarCloud will make this onboarding process easier for BitBucket Cloud, Azure Devops, and others.
-Users' permissions will be retrieved from systems and mapped to SonarCloud permissions on a best-effort basis.
\ No newline at end of file
+++ /dev/null
----
-title: Organization Visibility
-url: /organizations/organization-visibility/
----
-
-## Free plan organization
-
-Free plan organizations are public. This means that almost everything is visible to any user - even anonymous ones:
-
-* Projects
-* Issues
-* Quality Profiles
-* Quality Gates
-* Rules
-
-The following pages are restricted:
-
-* Members: to members of the organization
-* Administration pages: to administrators of the organization
-
-## Paid plan organization
-
-Paid plan organizations are private. This means that nothing is visible to non-members of the organization. In other words, you need to be a member of the organization to see:
-
-* Projects - which are private by default
-* Issues
-* Quality Profiles
-* Quality Gates
-* Rules
-* Members
-
-The administration pages are obviously also restricted to administrators of the organization.
-
-### Want to make one project public?
-
-If you are on a paid plan organization but want to make a project public (for instance because you are developing an open-source library), this is possible. You will have to manually make the project public in its **Administration > Permissions** page. Once done, you will notice the "Public" badge on the project.
-
-As soon as you have one public project, the following pages will become visible to any user:
-
-* Projects
-* Issues
-* Rules
-
-"Quality Profiles" and "Quality Gates" pages will remain restricted to members only - since you might not want to unveil some information used by your private projects.
+++ /dev/null
----
-title: Privacy Policy
-url: /privacy/
----
-
-The privacy policy specifies how data collected on this website is used. Thank you for visiting our website and your interest in our services and products. As the protection of your personal data is an important concern for us, we will explain below what information we collect during your visit to our website, as they are processed and whether or how these may be used.
-
-## PERSONAL DATA
-
-Personal information is data about personal or material circumstances of an identified or identifiable natural person. This includes information such as your first and last name, your postal or residential address, telephone numbers and date of birth. Information that can not be directly related to your real identity – such as your favorite websites or the number of users of a page – are not considered as personal data.
-
-## COLLECTION AND PROCESSING OF PERSONAL DATA
-
-As the operator and creator of the website, we do not store personal data itself automatically. If you go to our website, the provider – where the web server is hosted – may temporarily store data for the purpose of system security such as the connection of the computer, the web pages you visit, the date and duration of the visit, data about the used browser software and operating system and the web page from which you visit us. In addition to that, personal information such as your name, address, phone number or e-mail will only be stored, if you have provided this information voluntarily, eg. as part of a registration, a survey, a contest, to carry out an order or contract or an information request.
-
-## USE AND DISCLOSURE OF PERSONAL DATA
-
-Personal data you provided may be used solely for the purpose of technical website administration and to fulfill your wishes and requirements, thus primarily to processing the order with you or to respond to your request. Only if you have previously given your consent or – if stipulated by legal regulations – you entered no objection, we use this data for product surveys and marketing purposes. We don’t share, sell or transfer your personal data to third parties, unless this is necessary for the purpose of the contract or unless you have explicitly consented. For example it may be necessary, that in case of an product order we share your address and order with our suppliers.
-
-## USE OF WEB ANALYSIS SOFTWARE
-
-To improve the structure and the data we offer on our website, we might use open source or proprietary web analysis software. Our evaluations will be based on summary or averaged information amalgamated for the large numbers of people visiting the vebsite. The data provided by won’t be matched with any individual’s data from other sources.
-
-Data collected might include IP, time and duration of the visit, what pages are visited, used browser and add-ons/plugins, search-engines and referrer. While statistic tools might use a “cookie” to distinguish between individual visitors, the collected data doesn’t allow to identify individuals.
-
-## INFORMATION USED DURING AUTHENTICATION
-
-We use the following information for authentication with GitHub / Bitbucket / Azure DevOps.
-
-### GitHub
-* ID
-* Login
-* Name
-* Email
-* List of organizations the user is member of
-
-For more information:
-* https://developer.github.com/v3/users/#get-the-authenticated-user
-* https://developer.github.com/v3/users/emails/#list-email-addresses-for-a-user
-* https://developer.github.com/v3/orgs/#list-your-organizations
-
-### Bitbucket
-* UUID
-* Username
-* Display name
-* Email
-* Is email defined as primary
-
-For more information:
-* https://developer.atlassian.com/bitbucket/api/2/reference/resource/user
-* https://developer.atlassian.com/bitbucket/api/2/reference/resource/user/emails
-
-### Azure DevOps
-* Tenant ID
-* Object ID
-* Display name
-* User Principal Name
-* Email
-
-For more information:
-* https://docs.microsoft.com/en-us/graph/api/user-get?view=graph-rest-1.0
-
-## SECURITY
-
-We take all the necessary technical and organisational security measures to protect your personal data from loss and misuse. Your data is stored in a secure operating environment that is not accessible to the public. If you communicate with us via e-mail, please note that the confidentiality of the information is not guaranteed. The contents of e-mails can be intercepted by third parties. In case of doubt we therefore recommend to send confidential information only by snail mail.
-
-## RIGHT OF ACCESS TO PERSONAL DATA
-
-Upon written request you will be informed by us what information we stored about you (such as name or address).
-
-## CONTACT
-
-If you have questions regarding the processing of personal data or in case of requests for information, suggestions or complaints, please [contact us](/#sonarcloud#/about/contact) directly.
+++ /dev/null
----
-title: Security Statement
-url: /security/
----
-
-We know that your code is very important to you and your business. We also know that no one wants proven bugs or vulnerabilities found on their source code to be unveiled to third-parties. This is why we take security extremely seriously.
-
-## Hosting
-
-SonarCloud runs primarily off the AWS Frankfurt region. It also uses marginally services located in the AWS Ireland region when they are not available in Frankfurt.
-
-## System security
-
-SonarCloud uses its own Virtual Private Cloud (AWS VPC). Accesses to the infrastructure are restricted through firewalls, allowing accesses from SonarSource networks only. Secure protocols are required for accesses and SSL keys are used for authentication. Access to the infrastructure, inclusive of storage, is restricted to the Technology Operations team.
-
-
-## Data security
-
-At the infrastructure level, access to data is controlled by virtue of being hosted in network zones which only the Technology Operations have access to.
-
-To insure data availability, the SonarCloud database is replicated in quasi real time between 2 availability zones both within the Frankfurt region. In addition, the database is fully backed up every day with a 7 days retention.
-
-At the software level, SonarCloud ensures private source code is accessible to organization members only, in addition to SonarSource Technology Operations team for support purposes only.
-
-
-
-## Software security
-
-SonarCloud UI and APIs regularly pass penetration testing conducted by a an external company, specialized in cyber and application security, certified in accordance to ISO-27001 and which is also member of the OWASP.
-
-In case you find a vulnerability, please follow our [Responsible Vulnerability Disclosure process](https://community.sonarsource.com/t/responsible-vulnerability-disclosure/9317) to report it to our Security team.
-
-## Communications
-
-All communications are done over TLS and support TLS 1.2:
-* Navigating in the Web application
-* Using WS APIs
-* Running analysis (by the scanners) from CI services and pushing analysis reports to SonarCloud
-
-## SonarCloud Webhooks
-
-You can use secrets to secure webhooks and ensure they are coming from SonarCloud (see the "Securing your webhooks" section of the [Webhooks](/project-administration/webhooks/#securing-your-webhooks) page for more information).
-
-
-## Authentication
-
-Primary authentication on the system is available through the SonarCloud GitHub application, through OAuth authentication with Bitbucket Cloud and Microsoft Azure DevOps. As a consequence, users don’t have a password on SonarCloud, and are as protected as what they expect (especially with 2FA activated on those systems).
-
-For WS API calls or source code analysis triggered from CI services, only revocable user tokens are accepted.
-
-## Payment
-
-When you subscribe to the paid plan on SonarCloud, your credit card information never transit through our system nor it gets stored on the server. It's handed off to [Braintree Payment Solutions](https://www.braintreepayments.com), a company dedicated to storing your sensitive data on [PCI-Compliant](http://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard) servers.
+++ /dev/null
----
-title: Pricing
-url: /sonarcloud-pricing/
----
-
-Subscribing to a paid plan on SonarCloud allows you to analyze unlimited private projects, to know more about all the advantages of a paid plan check our [pricing page](/#sonarcloud#/about/pricing).
-
-## How do I activate the paid plan?
-
-You can activate the paid plan on the **Administration > Billing** page of your organization.
-
-## How do I get invoices?
-
-You can download PDF invoices for every payment from the **Administration > Billing** page of your organization.
-
-If you want to get invoices by email, go to **Administration > Billing > Edit billing info** and check "Send the monthly receipt to this email".
+++ /dev/null
----
-title: Supported languages
-url: /analysis/supported-languages/
----
-
-Here is the list of all the languages currently supported in SonarCloud :
-
-* [ABAP](https://redirect.sonarsource.com/plugins/abap.html)
-* [Apex](https://redirect.sonarsource.com/plugins/apex.html)
-* [C](https://redirect.sonarsource.com/plugins/cpp.html)
-* [C++](https://redirect.sonarsource.com/plugins/cpp.html)
-* [C#](https://redirect.sonarsource.com/plugins/csharp.html)
-* [Objective-C](https://redirect.sonarsource.com/plugins/objectivec.html)
-* [COBOL](https://redirect.sonarsource.com/plugins/cobol.html)
-* [CSS](https://redirect.sonarsource.com/plugins/css.html)
-* [Flex](https://redirect.sonarsource.com/plugins/flex.html)
-* [Go](https://redirect.sonarsource.com/plugins/go.html)
-* [HTML](https://redirect.sonarsource.com/plugins/web.html)
-* [Java](https://redirect.sonarsource.com/plugins/java.html)
-* [JavaScript](https://redirect.sonarsource.com/plugins/javascript.html)
-* [Kotlin](https://redirect.sonarsource.com/plugins/kotlin.html)
-* [PHP](https://redirect.sonarsource.com/plugins/php.html)
-* [PL/SQL](https://redirect.sonarsource.com/plugins/plsql.html)
-* [Python](https://redirect.sonarsource.com/plugins/python.html)
-* [Ruby](https://redirect.sonarsource.com/plugins/ruby.html)
-* [Scala](https://redirect.sonarsource.com/plugins/scala.html)
-* [Swift](https://redirect.sonarsource.com/plugins/swift.html)
-* [TypeScript](https://redirect.sonarsource.com/plugins/typescript.html)
-* [T-SQL](https://redirect.sonarsource.com/plugins/tsql.html)
-* [Visual Basic .NET](https://redirect.sonarsource.com/plugins/vbnet.html)
-* [XML](https://redirect.sonarsource.com/plugins/xml.html)
border-radius: 2px;
line-height: 20px;
font-size: var(--smallFontSize);
- color: var(--sonarcloudBlack100);
+ color: var(--white);
white-space: nowrap;
text-align: center;
font-weight: bold;
//promotion
darkBackground: '#292929',
darkBackgroundSeparator: '#413b3b',
- darkBackgroundFontColor: '#f6f8fa',
-
- // sonarcloud
- sonarcloudOrange500: '#fd6a00',
- sonarcloudOrange600: '#e26003',
- sonarcloudOrange700: '#db5700',
-
- sonarcloudBlack100: '#ffffff',
- sonarcloudBlack200: '#f9f9fb',
- sonarcloudBlack250: '#e6e8ea',
- sonarcloudBlack300: '#cfd3d7',
- sonarcloudBlack500: '#8a8c8f',
- sonarcloudBlack700: '#434447',
- sonarcloudBlack800: '#2d3032',
- sonarcloudBlack900: '#070706',
-
- sonarcloudBlue500: '#4c9bd6',
- sonarcloudBlue600: '#327bb3',
- sonarcloudBlue900: '#0b3c62',
-
- sonarcloudBorderGray: 'rgba(207, 211, 215, 0.5)'
+ darkBackgroundFontColor: '#f6f8fa'
},
sizes: {
.markdown-toc-content a {
display: block;
- color: var(--sonarcloudBlack900);
+ color: var(--baseFontColor);
padding: calc(var(--gridSize) / 2) var(--gridSize);
border: 1px solid white;
line-height: 1.2;
user.x_deleted={0} (deleted)
login.login_to_sonarqube=Log In to SonarQube
-login.login_or_signup_to_sonarcloud=Log in or Sign up to SonarCloud
login.login_with_x=Log in with {0}
login.more_options=More options
login.unauthorized_access_alert=You are not authorized to access this page. Please log in with more privileges and try again.
my_profile.password.changed=The password has been changed!
my_profile.notifications.submit=Save changes
my_profile.overall_notifications.title=Overall notifications
-my_profile.sonarcloud_feature_notifications.title=SonarCloud new feature notifications
-my_profile.sonarcloud_feature_notifications.description=Display a notification in the header when new features are deployed
my_profile.per_project_notifications.title=Notifications per project
my_profile.per_project_notifications.add=Add a project
my_profile.per_project_notifications.edit=Set notifications
permission_template.default_for=Default for {0}
permission_templates.project_creators=Creators
permission_templates.project_creators.explanation=When a new project, portfolio or application is created, the user who creates it will receive these permissions.
-permission_templates.project_creators.explanation.sonarcloud=When a new project is created, the user who creates it will receive these permissions.
permission_templates.bulk_apply_permission_template=Bulk Apply Permission Template
permission_templates.bulk_apply_permission_template.apply_to_selected=You're about to apply the selected permission template to {0} selected item(s).
permission_templates.bulk_apply_permission_template.apply_to_all=You're about to apply the selected permission template to {0} item(s).
overview.badges.measure.description.TRK=Displays the current status of one metric of your project.
overview.badges.measure.description.VW=Displays the current status of one metric of your portfolio.
overview.badges.measure.description.APP=Displays the current status of one metric of your application.
-overview.badges.marketing.alt=Scanned on SonarCloud badge
-overview.badges.marketing.description=This badge lets you advertise that you're using SonarCloud for code quality.
-overview.badges.marketing.description.TRK=This badge lets you advertise that you're using SonarCloud for code quality.
overview.badges.quality_gate.alt=Quality Gate badge
overview.badges.quality_gate.description=Displays the current quality gate status of your project.
overview.badges.quality_gate.description.APP=Displays the current quality gate status of your application.
# EMBEDED DOCS
#
#------------------------------------------------------------------------------
-embed_docs.blog=Blog
embed_docs.documentation=Documentation
embed_docs.get_help=Get Help
-embed_docs.latest_blog=Latest blog
embed_docs.news=Product News
embed_docs.stay_connected=Stay Connected
embed_docs.suggestion=Suggestions For This Page
-embed_docs.whats_new=What's new on SonarCloud?
#------------------------------------------------------------------------------
#
onboarding.analysis.java.maven.header=Execute the Scanner for Maven
-onboarding.analysis.java.maven.header.ci=Execute the Scanner for Maven from your CI
onboarding.analysis.java.maven.text=Running a {instance} analysis with Maven is straighforward. You just need to run the following command in your project's folder.
onboarding.analysis.java.maven.docs_link=official documentation of the Scanner for Maven
onboarding.analysis.java.maven.text.custom=Run the following command in your project's folder.
-onboarding.analysis.java.maven.text.custom.ci=Run the following command in the project's folder.
-onboarding.analysis.java.maven.header.sonarcloud=Execute the Scanner for Maven from Travis
-onboarding.analysis.java.maven.text.sonarcloud=Add the following lines to your <code>.travis.yml</code> file:
onboarding.analysis.java.gradle.header=Execute the Scanner for Gradle
-onboarding.analysis.java.gradle.header.ci=Execute the Scanner for Gradle from your CI
onboarding.analysis.java.gradle.text.1=Running an analysis with Gradle is straighforward. You just need to declare the {plugin_code} plugin in your {filename} file:
onboarding.analysis.java.gradle.text.2=and run the following command:
onboarding.analysis.java.gradle.latest_version=You can find the latest version of the Gradle plugin {link}.
onboarding.analysis.java.gradle.docs_link=official documentation of the Scanner for Gradle
-onboarding.analysis.java.gradle.header.sonarcloud=Execute the Scanner for Gradle from Travis
-onboarding.analysis.java.gradle.text.1.sonarcloud=Declare the {plugin} plugin in your {file} file:
-onboarding.analysis.java.gradle.text.2.sonarcloud=and add the following lines to your {file} file:
onboarding.analysis.msbuild.header=Download and unzip the Scanner for .NET
onboarding.analysis.msbuild.text=Visit the {link} to download the latest version, and add the executable's directory to the {code} environment variable
projects / sonarqube.git / commitdiff