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 71 Next »

NameHudson/Jenkins Plugin
Latest version1.8.1 (2 February 2012)
DownloadUse Hudson/Jenkins Update Center
LicenseGNU LGPL 3
DevelopersSonarSource
Issue trackerSONARPLUGINS/component/13726
Sourceshttps://github.com/SonarSource/jenkins-sonar-plugin

Description / Features

The plugin enables to trigger Sonar analysis from Hudson/Jenkins.

Installation

  1. Installing Sonar
  2. Installing Jenkins
  3. Installing the Sonar Jenkins plugin via the Update Center

Before upgrading please read the upgrade guide.

Usage

  1. Configuring Sonar Jenkins Plugin
  2. Triggering Sonar on Jenkins Job

The analysis of projects by Sonar will add time to the build process of your projects. For continuous inspection of your projects, we advice to run one Sonar analysis a day.

Depending on your needs, you can achieve that by:

  • cloning your Jenkins job and add build it one time a day,
  • or using the trigger functionality to prevent the execution of Sonar for builds that are triggered by SCM or by dependencies.

We suggest to use the trigger functionality as it will prevent duplication of your projects.

Advanced Topics

Change Log

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

Release 1.7

Icon

Don't use this version as it contains critical bug - SONARPLUGINS-1455

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

Icon

Before upgrade please make a backup of your Hudson configuration and carefully read following notes.

Icon

If you are using version above 1.2, then before upgrade make sure that your jobs was saved with proper configuration. In order to do it, execute following script from Hudson Script Console:

Icon

If you are using version below 1.2, then:

  1. download version 1.2.2 or 1.3.1
  2. perform manual upgrade, using Manage Plugins -> Advanced -> Upload Plugin
  3. perform automatic upgrade to version 1.4 (see instructions above)

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

Icon

This version introduces some changes to configuration files. Upgrade will be performed automatically, but before upgrade please make a backup of your Hudson configuration.

Icon

Most probably next plugin version will be incompatible with versions below 1.2, so it's highly recommended to update to this version.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

Icon

When upgrading to this version, please be aware that "Skip on SCM build" (Default Yes) is becoming "Poll SCM" (Default No) under Triggers section. Due to technical limitation, this data could not be migrated to 1.1, and therefore if it was unchecked in certain jobs, the new box should be manually checked.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

com.atlassian.confluence.macro.MacroExecutionException: JIRA project does not exist or you do not have permission to view it.

 

  • No labels