CLI had same issue and after oparent fix, sonar build is successful . Thanks 
Gary. 


***************************************************************************************
本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!**************************************************************************************

***************************************************************************************
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***************************************************************************************

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Gary Wu via RT
Sent: 22 August 2017 04:09
Cc: [email protected]
Subject: [onap-discuss] [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

_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to