+ ONAP release Dear ONAP team,
Following up with this task, I have made sure all Sonar jobs ran at least once. I fixed few infra issues and here are the latest issues we got: *Compilation/Dependency error:* https://jenkins.onap.org/view/01-all-sonar/job/aai-aai-servi ce-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/aai-rest-clie nt-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/clamp-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/policy-engine-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/vvp-jenkins-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/ccsdk-distrib ution-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/vnfsdk- compliance-sonar/2/console https://jenkins.onap.org/view/01-all-sonar/job/usecase-ui-sonar/2/ *Need plugin version changes:* https://jenkins.onap.org/view/01-all-sonar/job/aai-sparky-fe-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/ccsdk-platfor m-plugins-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/ccsdk-storage -pgaas-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/dcaegen2-plat form-configbinding-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/oom-registrat or-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/oparent-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/ui-dmaapbc-sonar/2/console *Test failures:* https://jenkins.onap.org/view/01-all-sonar/job/aai-traversal-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/policy-common-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/policy-drools -pdp-sonar/1/console https://jenkins.onap.org/view/01-all-sonar/job/appc-sonar/1/console I am looking into the plugin version job failures and should be a matter or making the updates in the pom files for some of them. Please look into your job's compilations/test failures and let me know for any questions Thanks a ton! Jess On Thu, Feb 1, 2018 at 1:00 PM, Jessica Wagantall < [email protected]> wrote: > Dear ONAP team, > > As few of you pointed out, after creating our amsterdam branch, we started > seeing some issues > in Sonar after the scans were trying to get processed for this branch as > well as master. As you might > know, Sonar does not have a concept of branching and hence we decided to > focus our scans to just > the master branch. > > Our gerrit-maven-sonar job from global-jjb takes care of handling this > properly. This is why, we have > now switched from using our internal Sonar task (from > release_version_java_daily jobs) to use the > one LF team developed in global-jjb. > > This is the reference change if you want to take a look at it: > https://gerrit.onap.org/r/#/c/29561/ > > All Sonar jobs are now located in the following view: > https://jenkins.onap.org/view/01-all-sonar/ > These jobs are scheduled to run every Saturday but anyone can run it in > demand after posting a > comment "run-sonar" in your Gerrit change. > > I am running all of them once and detecting any failures to make sure we > are on track. > > Please let me know for any questions! > Thanks! > Jess >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
