Hi Gary, Jessica,
This job has similar issue:
msb-apigateway-master-stage-site-java
https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/msb-apigateway-master-stage-site-java/3/console.log.gz
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.6:stage-deploy (default-cli) on
project msb-apigateway-parent: Error uploading site: Failed to transfer file:
https://nexus.onap.org/content/sites/site/org/onap/msb/apigateway/1.0.0/staging/./dependencies.html.
Return code is: 401 -> [Help 1]
Could you please help me with that?
Thanks,
Huabing
Original Mail
Sender: <[email protected]>
To:
CC: <[email protected]>zhaohuabing10201488
Date: 2017/08/22 06:39
Subject: [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue
Hi Huabing,
I've incorporated the staging plugin config below into oparent, and it looks
like the MSB release-version jobs are completing successfully now.
Thanks,
Gary
-----Original Message-----
From: Jessica Wagantall via RT [mailto:[email protected]]
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu <[email protected]>
Cc: [email protected] [email protected]
Subject: [ONAP Helpdesk #44285] RE: MSB Jenkins job issue
Sure, of course.
Basically the pom.xml needs to be containing the repositories, distribution
management and staging plugin blocks.
Let's take the vid pom.xml as an example of the information your pom is
missing.
Basically, the staging plugin definition needs to look like this:
<plugin>
<groupId>org.sonatype.plugins</groupId>
<artifactId>nexus-staging-maven-plugin</artifactId>
<version>1.6.7</version>
<extensions>true</extensions>
<configuration>
<nexusUrl>${nexusproxy}</nexusUrl>
<stagingProfileId>176c31dfe190a</stagingProfileId>
<serverId>ecomp-staging</serverId>
</configuration>
</plugin>
You will also need the definition for the repositories, which looks like this:
<repositories>
<repository>
<id>ecomp-releases</id>
<name>VID Release Repository</name>
<url>${nexusproxy}/${releaseNexusPath}</url>
</repository>
<repository>
<id>ecomp-snapshots</id>
<name>VID Snapshot Repository</name>
<url>${nexusproxy}/${snapshotNexusPath}</url>
</repository>
<repository>
<id>ecomp-staging</id>
<name>VID Staging Repository</name>
<url>${nexusproxy}/${stagingNexusPath}</url>
</repository>
<repository>
<!-- Snapshots repository has ECOMP
snapshot artifacts -->
<id>oss-snapshots</id>
<name>oss Central - Snapshots</name>
<url>https://oss.sonatype.org/service/local/repositories/releases/content/</url>
</repository>
</repositories>
Notice that the serverIDs are prefixed like "ecomp-" and not "onap-". This is a
rename that still hasn't changed, but we are discussing about the impact on
doing so.
Lastly, you will also need to update the distribution management:
<distributionManagement>
<repository>
<id>ecomp-releases</id>
<name>VID Release Repository</name>
<url>${nexusproxy}/${releaseNexusPath}</url>
</repository>
<snapshotRepository>
<id>ecomp-snapshots</id>
<name>VID Snapshot Repository</name>
<url>${nexusproxy}/${snapshotNexusPath}</url>
</snapshotRepository>
<!-- added for javadoc -->
<site>
<id>ecomp-site</id>
<url>dav:${nexusproxy}${sitePath}</url>
</site>
</distributionManagement>
Please feel free to add me as reviewer to your pom.xml changes and I can help
further.
I hope this information helps
Thanks!
Jess_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
