Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 58 Next »

Table of Contents

Only project administrators can access project settings (See Security).

Adding a Project

Adding a project to SonarQubeTM is not done through the web interface, but automatically when the project is analyzed for the first time.

Deleting a Project

You can delete a project by clicking on Project Deletion in the left menu.

Note that a service to delete several projects at the same time is available since version 3.2.

Updating Project Key

Since version 3.2, the project key can be updated. Go to Configuration > Update Key:


Setting Quality Profiles

As version 3.3 enables multi-language project analysis, project administrators can select which quality profile to use for each language on their project. Go to Settings > Quality Profiles:

Excluding Files

It is possible to exclude files from being analyzed:

  • Since version 3.3, go to Configuration > Settings > Exclusions and set the sonar.exclusions property.
  • For versions prior to 3.3, click on Exclusions in the left menu and set the sonar.exclusions property.
Since version 3.3, it is also possible to:
  • Exclude tests file from being analyzed: go to Configuration > Settings > Exclusions and set the sonar.tests.exclusions property
  • Set global exclusions that will apply to all the projects: go to Configuration > General Settings > Exclusions and set the and properties.


Coding rules


If you want to exclude source code from being check against some coding rules, you can have a look at the Switch Off Violations plugin.

Since version 3.5, it is also possible to:

  • Set the files to be analyzed through the sonar.inclusions and sonar.test.inclusions properties. In this case, only these very files will be analyzed.
  • Exclude some files from being checked against duplications. To do so, set the through the sonar.cpd.exclusions property (Configuration > Settings > Duplications).

There are two different ways to exclude/include files:

  • Fully qualified name of the resource (see red frames below):

    For Java only, replace '.' package separator by '/' and add '.java' extension.


  • Absolute path:


Full documentation is directly available on the SonarQubeTM web interface (Configuration > Settings > Exclusions).

Customizing Links

To add links to your project, click on Links in the left menu:

They are two types of links:

These links have to be defined in the analysis configuration file:

  • Home: sonar.links.homepage
  • Continuous integration:
  • Issue tracker: sonar.links.issue
  • Sources: sonar.links.scm
  • Developer connection: sonar.links.scm_dev

For Maven projects, these links are retrieved from the project POM:

  • Home: <url>
  • Continuous integration: <ciManagement><url>
  • Issue tracker: <issueManagement><url>
  • Sources: <scm><url>
  • Developer connection: <scm><developerConnection>
Setting a sonar.links.* property on a Maven project overrides the one above.
These links can be displayed on a:
  • Filter by adding the Link column
  • Dashboard by adding the Description widget

They can not be modified through the web interface.

Any link can be added trough the web interface.

Those links can be displayed on a dashboard by adding the Description widget.

Configuring Plugins

Several plugins can be configured at project level to override Global Settings for that project. On your project, click on Configuration in the top right corner.

  • No labels