ubject: 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
intr
uss] [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.
g] On Behalf Of Guangrong Fu via RT
Sent: Wednesday, August 30, 2017 8:32 AM
Cc: onap-discuss@lists.onap.org
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 includ
g] On Behalf Of Guangrong Fu via RT
Sent: Wednesday, August 30, 2017 8:32 AM
Cc: onap-discuss@lists.onap.org
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 includ
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
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:
3.8
jacoco
${project.build.directory}/code-coverage/jacoco.exec
${project.build.directory}/code-coverage/jacoco-it.exec
Dear Guangrong,
I am not too familiar with the sonar code coverage setup.
But I can see that the log is showing the following information:
11:36:49 [INFO] JaCoCoSensor: JaCoCo report not found :
/w/workspace/holmes-dsa-master-release-version-java-daily/dmaap-dsa/target/jacoco.exec
11:36:49 [INF
Dear Guangrong,
The last job failed with a known error that we are seeing from time to time and
looks like it is a connection glitch.
All jobs are failing due to the missing version.properties file that needs to
be in each repo at the root level. Take for example so repo (file
so/version.pro
