Differences between revisions 18 and 19
Revision 18 as of 2015-12-09 08:14:47
Size: 1863
Editor: HerveBoutemy
Comment: BUILDS jira project was shut down, replaced by INFRA with Analysis component
Revision 19 as of 2015-12-09 08:18:40
Size: 1925
Editor: HerveBoutemy
Comment: added notification field
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
To prevent opening MySql access to some others machines, Sonar builds will be done on a local Jenkins instance at https://analysis.apache.org/jenkins/ To prevent opening MySql access to some others machines, Sonar builds are done on a local Jenkins instance at https://analysis.apache.org/jenkins/
Line 19: Line 19:
 * notification mailing list: notification@tlp.apache.org (e.g.)

Sonar Instance at Apache

A Sonar instance is now available at https://analysis.apache.org.

To prevent opening MySql access to some others machines, Sonar builds are done on a local Jenkins instance at https://analysis.apache.org/jenkins/

To add your project, you should create a Jira issue: https://issues.apache.org/jira/browse/INFRA (component: "Analysis") see sample: https://issues.apache.org/jira/browse/INFRA-10357.

The Jira entry must contain:

  • svnurl: http://svn.apache.org/repos/asf/maven/scm/trunk/ (e.g.)

  • pom path: (blank as svnurl/pom.xml)
  • Maven version: 3.0.5 (e.g.)

  • jdk version: jdk1.8 jdk1.7 jdk1.6 jdk1.5

  • Maven profiles to use: (leave blank if none, please use comma if multiple profiles to activate: foo,bar )

  • Maven build properties: (leave blank if none, if some to activate, please format: -Dmyprop=foo -Dbar=beer )

  • Sonar build options (if any)
  • notification mailing list: notification@tlp.apache.org (e.g.)

Sonar builds will run @daily and will be triggered only in case of scm changes.

A first Maven build will be executed to validate the project and compile sources for Findbugs analysis: mvn clean install -DskipTests.

The INFRA/Analysis jira is maintained by the BUILDS community and via the Mailing List at builds@apache.org - you should ensure you are signed up. If a INFRA/Analysis jira has not been replied to within a few days feel free to ping the builds mailing list mentioning the Jira issue number. Remember that the builds mailing list and INFRA/Analysis jira are maintained by volunteers so do allow appropriate time for a response.

Should a response not be achieved on a INFRA/Analysis ticket or a builds.at.a.o mailing list email after 2 weeks, feel free to escalate the issue by sending an email to the infrastructure team with details of the INFRA ticket who will then follow up on the issue.

Thanks.

SonarInstance (last edited 2015-12-09 08:18:40 by HerveBoutemy)