Thanks, Gary. Let's check it after the daily build is completed later today. Regards,GuangrongOn 08/31/2017 06:30, Gary Wu (mailto:[email protected]) wrote:
Hi Guangrong, The enforcer checks in oparent 1.0.0-SNAPSHOT have been changed to warnings now, and your job should complete successfully once it's re-triggered. Thanks, Gary -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Guangrong Fu via RT Sent: Wednesday, August 30, 2017 8:32 AM Cc: [email protected] Subject: Re: [onap-discuss] [ONAP Helpdesk #44749] Help is Needed for Jenkins Job Failure Dear Jess, Thanks for your information. Actually the code fragment you provided is already included in the pom file of OPARENT. The reason for the absence of the *.exec file is that we introduced the org.onap.oparent:version:1.0.0-SNAPSHOT rather than org.onap.oparent:parent:1.0.0-SNAPSHOT as our parent pom by mistake. Now it's fixed and we can see the jacoco-ut.exec on our local machine. So let's check whether Sonar could find it or not. Unfortunately, problems keep rising: Two of our *-release-version-java jobs have been failing recently. The explicit error we get is as follows: *12:27:39* [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (enforce-no-snapshots) on project holmes-rulemgt: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1]*12:27:39* [ERROR] *12:27:39* [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.*12:27:39* [ERROR] Re-run Maven using the -X switch to enable full debug logging.*12:27:39* [ERROR] *12:27:39* [ERROR] For more information about the errors and possible solutions, please read the following articles:*12:27:39* [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException*12:27:39* [ERROR] *12:27:39* [ERROR] After correcting the problems, you can resume the build with the command*12:27:39* [ERROR] mvn <goals> -rf :holmes-rulemgt It seems to be caused by the following problem about which I am not totally sure : Found Banned Dependency: org.onap.holmes.common:holmes-actions:jar:1.0.0-SNAPSHOT Could you please help to take a look at it? For another job, the failure is caused by the connection issue: [ERROR] SonarQube server [https://sonar.onap.org] can not be reached Only all of these issues are fixed can we get to know whether the changes in the pom files are correct. So I wish all of the problems above could be solved as soon as possible. Thanks. Guangrong Best Regards, Guangrong On Wed, Aug 30, 2017 at 5:19 AM, Jessica Wagantall via RT < [email protected]> wrote: > Dear Guangrong, > > my team member Thanh confirmed that there is this basic configuration > needed. Here is an example from what ODL has in one of their repos: > > <!-- Default Sonar configuration --> > <sonar-jacoco-listeners.version>3.8</sonar-jacoco-listeners.version> > <sonar.core.codeCoveragePlugin>jacoco</sonar.core.codeCoveragePlugin> > <sonar.jacoco.reportPath>${project.build.directory}/code- > coverage/jacoco.exec</sonar.jacoco.reportPath> > <sonar.jacoco.itReportPath>${project.build.directory}/code- > coverage/jacoco-it.exec</sonar.jacoco.itReportPath> > <!-- Note: This list should match jacoco-maven-plugin's exclusion > list below --> > <sonar.exclusions>**/gen/**,**/generated-sources/**,**/ > generated-test-sources/**,**/yang-gen/**,**/yang-gen- > config/**,**/yang-gen-sal/**,**/yang-gen-code/**,**/pax/**</ > sonar.exclusions> > > > Please let me know if this helps. > Thanks! > Jess > > _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
