Hi Gary,
We're facing similar issues
msb-discovery-master-docker-java-version-shell-dailyDownloaded:
https://nexus.onap.org/content/repositories/public/org/apache/maven/maven-compat/3.0/maven-compat-3.0.jar
(279 KB at 464.5 KB/sec)
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps failed
with message:
Found Banned Dependency:
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
msb-apigateway-master-docker-java-version-shell-daily12:54:17 [WARNING] Rule 0:
org.apache.maven.plugins.enforcer.RequireReleaseDeps failed with
message:12:54:17 Found Banned Dependency:
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT12:54:17 Use 'mvn
dependency:tree' to locate the source of the banned dependencies.
msb-discovery-master-release-version-java-daily[INFO] ---
maven-enforcer-plugin:3.0.0-M1:enforce (enforce-no-snapshots) @
msb-discovery-parent ---
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps failed
with message:
Found Banned Dependency:
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT
Use 'mvn dependency:tree' to locate the source of the banned
dependencies.msb-swagger-sdk-master-release-version-java-daily[INFO] ---
maven-enforcer-plugin:3.0.0-M1:enforce (enforce-no-snapshots) @ swagger-sdk ---
[WARNING] The artifact org.apache.commons:commons-io:jar:1.3.2 has been
relocated to commons-io:commons-io:jar:1.3.2
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps failed
with message:
Found Banned Dependency:
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
There is also another issue rising says "Failed to download dependencies"
Project msb-apigateway-master-stage-site-javaFailed to download
dependenciesProject org.onap.msb.apigateway.apiroute:apiroute-service:jar:1.0.0
could not be built, as one of its dependency chain,
io.dropwizard:dropwizard-core:jar:0.8.0 ->
io.dropwizard:dropwizard-validation:jar:0.8.0 ->
org.hibernate:hibernate-validator:jar:5.1.3.Final: Failed to read artifact
descriptor for org.hibernate:hibernate-validator:jar:5.1.3.Final failed to
resolve, because we could not download artifact {
org.onap.msb.apigateway.apiroute:apiroute-service:jar:1.0.0,3} from repository
{ org.onap.msb.apigateway.apiroute:apiroute-service:jar:1.0.0,4}. Reported
cause was: 504 , ReasonPhrase:Gateway Time-out..Thanks,
Huabing
Original Mail
Sender: <[email protected]>
To: <[email protected]>
CC: <[email protected]>
Date: 2017/08/31 05:59
Subject: Re: [onap-discuss] [integration][vnfsdk] Daily build failing due
tosome banned dependencies.
Hi Skip,
The short answer is no later than RC0 (Sept. 28th).
The long answer is that it may depend on the rollout schedule of
https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process,
which I will introduce to the community shortly.
Thanks,
Gary
From: WONNELL, SKIP [mailto:[email protected]]
Sent: Wednesday, August 30, 2017 1:39 PM
To: Gary Wu <[email protected]>
Cc: [email protected]
Subject: RE: [onap-discuss] [integration][vnfsdk] Daily build failing due to
some banned dependencies.
Thanks Gary,
What is the schedule for reverting the checks back to errors?
Skip
From: Gary Wu [mailto:[email protected]]
Sent: Wednesday, August 30, 2017 3:27 PM
To: WONNELL, SKIP <[email protected]>
Cc: [email protected]
Subject: RE: [onap-discuss] [integration][vnfsdk] Daily build failing due to
some banned dependencies.
Hi Skip,
I’ve changed the enforcer checks to just warnings now, and your job has
completed successfully.
Thanks,
Gary
From: WONNELL, SKIP [mailto:[email protected]]
Sent: Wednesday, August 30, 2017 12:22 PM
To: Gary Wu <[email protected]>
Subject: RE: [onap-discuss] [integration][vnfsdk] Daily build failing due to
some banned dependencies.
Hi Gary,
We continue to see a similar issue in the APPC daily release build:
https://jenkins..onap.org/job/appc-master-release-version-java-daily/189/
13:45:58 [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce
(enforce-no-snapshots) @ appc-common ---
13:45:58 [WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps
failed with message:
13:45:58 Found Banned Dependency:
org.openecomp.sdnc.core:dblib-provider:jar:1.1.2-SNAPSHOT
13:45:58 Use 'mvn dependency:tree' to locate the source of the banned
dependencies.
13:45:58 [INFO]
13:45:58 [INFO]
------------------------------------------------------------------------
13:45:58 [INFO] Skipping APP-C
13:45:58 [INFO] This project has been banned from the build due to previous
failures.
13:45:58 [INFO]
------------------------------------------------------------------------
I’m sure we’ve overlooked something, but your help would be appreciated.
Thanks,
Skip Wonnell
From: [email protected]
[mailto:[email protected]] On Behalf Of Gary Wu
Sent: Wednesday, August 30, 2017 1:30 PM
To: Murali p <[email protected]> [email protected]
Cc: [email protected]
Subject: Re: [onap-discuss] [integration][vnfsdk] Daily build failing due to
some banned dependencies.
Hi Murali,
In order to support Independent Versioning and Release, O-Parent is in active
development to add enforcement checks against SNAPSHOT dependencies this had
temporarily caused any SNAPSHOT dependencies to fail for staging or release
builds.
For the time being I’m relaxing the enforcement checks in oparent
1.0.0-SNAPSHOT until the process is fully rolled out. I’ve re-triggered your
job and it has completed successfully now.
Thanks,
Gary
From: Murali p
Sent: Wednesday, August 30, 2017 6:44 AM
To: [email protected]
Cc: Gary Wu <[email protected]> Andrew Grimberg
<[email protected]>
Subject: [vnfsdk] Daily build failing due to some banned dependencies.
Dear All,
The build failed due to some banned dependency. How to find the banned
dependency ? Please help.
https://jenkins.onap.org/view/vnfsdk/job/vnfsdk-refrepo-master-release-version-java-daily/lastBuild/console
11:24:23 [INFO] 11:24:23 [INFO] --- maven-enforcer-plugin:3..0.0-M1:enforce
(enforce-no-snapshots) @ vnfmarket --- 11:24:23 [WARNING] Rule 0:
org.apache.maven.plugins.enforcer.RequireReleaseDeps failed with message:
11:24:23 Found Banned Dependency:
org.onap.oparent:version-check-maven-plugin:jar:1.0.0-SNAPSHOT 11:24:23 Use
'mvn dependency:tree' to locate the source of the banned dependencies. 11:24:23
[INFO]
11:24:23 [INFO]
------------------------------------------------------------------------
11:24:23 [INFO] Skipping vnfmarket 11:24:23 [INFO] This project has been banned
from the build due to previous failures. 11:24:23 [INFO]
------------------------------------------------------------------------
11:24:23 [INFO]
------------------------------------------------------------------------
11:24:23 [INFO] Reactor Summary: 11:24:23 [INFO] 11:24:23 [INFO]
vnf-sdk-marketplace-core-parent .................... SUCCESS [ 46.824 s]
11:24:23 [INFO] vnf-sdk-marketplace/vnf-sdk-marketplace ............ SUCCESS
[03:24 min] 11:24:23 [INFO] vnf-sdk-marketplace/deployment
..................... SUCCESS [ 15.679 s] 11:24:23 [INFO] vnfmarket/deployment
................................ SUCCESS [ 0.524 s] 11:24:23 [INFO]
vnfmarket/deployment/docker ......................... SUCCESS [ 16.403 s]
11:24:23 [INFO] vnfmarket ........................................... FAILURE [
0.014 s] 11:24:23 [INFO]
------------------------------------------------------------------------
11:24:23 [INFO] BUILD FAILURE 11:24:23 [INFO]
------------------------------------------------------------------------
11:24:23 [INFO] Total time: 04:54 min 11:24:23 [INFO] Finished at:
2017-08-30T11:24:23+00:00 11:24:23 [INFO] Final Memory: 63M/406M 11:24:23
[INFO] ------------------------------------------------------------------------
11:24:23 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce
(enforce-no-snapshots) on project vnfmarket: Some Enforcer rules have failed.
Look above for specific messages explaining why the rule failed. -> [Help 1]
11:24:23 [ERROR] 11:24:23 [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e switch. 11:24:23 [ERROR] Re-run Maven using the -X
switch to enable full debug logging. 11:24:23 [ERROR] 11:24:23 [ERROR] For more
information about the errors and possible solutions, please read the following
articles: 11:24:23 [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
11:24:23 [ERROR] 11:24:23 [ERROR] After correcting the problems, you can resume
the build with the command 11:24:23 [ERROR] mvn <goals> -rf :vnfmarket
11:24:23 Build step 'Invoke top-level Maven targets' marked build as failure
11:24:23 $ ssh-agent -k 11:24:23 unset SSH_AUTH_SOCK 11:24:23 unset
SSH_AGENT_PID 11:24:23 echo Agent pid 1883 killed 11:24:23 [ssh-agent] Stopped.
11:24:23 [PostBuildScript] - Execution post build scripts.
Thanks,
Murali_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
