added link to migration info
added link to announce of old SOnar instance closing
|Deletions are marked like this.||Additions are marked like this.|
|Line 9:||Line 9:|
||| See [[https://lists.apache.org/thread.html/2d16db46d62d260a3763cb49e1c1d17411c9b41af8fd352d08167a3d@%3Cusers.infra.apache.org%3E|details on email@example.com]] |||||| See [[https://lists.apache.org/thread.html/2d16db46d62d260a3763cb49e1c1d17411c9b41af8fd352d08167a3d@%3Cusers.infra.apache.org%3E|details on firstname.lastname@example.org]] and [[https://lists.apache.org/thread.html/27807d84bf37638fdce83ecf8db278877623bda7f689d62a42096da9@%3Cbuilds.apache.org%3E|follow-up on email@example.com]] |||
Sonar Instance at Apache
A Sonar instance is now available at https://analysis.apache.org.
2016-12-17 Breaking News
This requirement of separate Jenkins server is over: migration to https://builds.apache.org/analysis starts
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: firstname.lastname@example.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 email@example.com - 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.