subject:"\[onap\-discuss\] \[integration\]\[ONAP Helpdesk #44285\] RE\: MSB Jenkins job issue"

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-23 Thread zhao.huabing

Thanks, Gray.

Besides, is it possible to move the ecomp-site configuration to Oparent POM? I 
think it's a common setting for all the project.







Original Mail



Sender:  <onap-helpd...@rt.linuxfoundation.org>
To: 
CC:  <onap-discuss@lists.onap.org>zhaohuabing10201488
Date: 2017/08/24 05:52
Subject: RE: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue





Hi Huabing,

I suspect the issue is that the site ID in your distributionManagement tags is 
“onap-site”.  I believe the expected value is “ecomp-site”.

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
Sent: Tuesday, August 22, 2017 6:53 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue


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<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:  
<onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>>
To:
CC:  
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>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:onap-helpd...@rt.linuxfoundation.org]
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging




You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/https://oss.sonatype.org/service/local/repositories/releases/content/%3c/url>>



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:


ecomp-releases
V

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-23 Thread zhao.huab...@zte.com.cn via RT

Thanks, Gray.

Besides, is it possible to move the ecomp-site configuration to Oparent POM? I 
think it's a common setting for all the project.







Original Mail



Sender:  <onap-helpd...@rt.linuxfoundation.org>
To: 
CC:  <onap-discuss@lists.onap.org>zhaohuabing10201488
Date: 2017/08/24 05:52
Subject: RE: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue





Hi Huabing,

I suspect the issue is that the site ID in your distributionManagement tags is 
“onap-site”.  I believe the expected value is “ecomp-site”.

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
Sent: Tuesday, August 22, 2017 6:53 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue


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<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:  
<onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>>
To:
CC:  
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>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:onap-helpd...@rt.linuxfoundation.org]
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging




You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/https://oss.sonatype.org/service/local/repositories/releases/content/%3c/url>>



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:


ecomp-releases
V

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-23 Thread Gary Wu via RT

Hi Huabing,

I suspect the issue is that the site ID in your distributionManagement tags is 
“onap-site”.  I believe the expected value is “ecomp-site”.

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
Sent: Tuesday, August 22, 2017 6:53 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue


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<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:  
<onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>>;
To:
CC:  
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;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:onap-helpd...@rt.linuxfoundation.org]
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging




You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/https://oss.sonatype.org/service/local/repositories/releases/content/%3c/url>>



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:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Re

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-23 Thread Gary Wu

Hi Huabing,

I suspect the issue is that the site ID in your distributionManagement tags is 
“onap-site”.  I believe the expected value is “ecomp-site”.

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
Sent: Tuesday, August 22, 2017 6:53 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue


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<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:  
<onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>>;
To:
CC:  
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;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:onap-helpd...@rt.linuxfoundation.org]
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging




You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/https://oss.sonatype.org/service/local/repositories/releases/content/%3c/url>>



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:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Re

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-22 Thread zhao.huab...@zte.com.cn via RT

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:  
To: 
CC:  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:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org zhao.huab...@zte.com.cn
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging

 


You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/



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:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}



ecomp-site
dav:${nexusproxy}${sitePath}





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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-22 Thread zhao.huabing

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:  
To: 
CC:  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:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org zhao.huab...@zte.com.cn
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging

 


You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/



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:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}



ecomp-site
dav:${nexusproxy}${sitePath}





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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-22 Thread Kanagaraj Manickam

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: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu via RT
Sent: 22 August 2017 04:09
Cc: onap-discuss@lists.onap.org
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:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org; zhao.huab...@zte.com.cn
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging

 


You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/



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:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}



ecomp-site
dav:${nexusproxy}${sitePath}





Please feel free to add me as reviewer to your pom.xml changes and I can help 
further. 

I hope this info

[onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-21 Thread Gary Wu via RT

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:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org; zhao.huab...@zte.com.cn
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging

 


You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/



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:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}



ecomp-site
dav:${nexusproxy}${sitePath}





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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

2017-08-21 Thread Gary Wu

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:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org; zhao.huab...@zte.com.cn
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:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging

 


You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/



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:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}



ecomp-site
dav:${nexusproxy}${sitePath}





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
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

[onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

[onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

9 matches

Site Navigation

Mail list logo

Footer information