Greetings Jess, Holmes is facing the same problem, too. Since some projects are still under devlopment, I think SNAPSHOT versions are better for the moment. It promises that the components which depend on others could retrieve the latest version of codes/updates from the nexus repo.
Best Regards,Guangrong On 01/4/2018 09:15， Jessica Wagantall via RT<[email protected]> (mailto:[email protected]) wrote： Although that can sound like the fastest way to fix it, is is best to move away from Snapshot dependencies as per these strategies: https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-Whatarethe2bigissuestoaddress? Thanks! Jess On Tue Jan 02 22:01:53 2018, [email protected] wrote: > I mean, could we just use the snapshot artifacts for these Jenkins > jobs? > > > Before the release of 1.0.0, all jenkins jobs ran very well. Should I > modify these jobs or pom.xml to use snapshot instead of release? > > > > > > > > > > > > Original Mail > > > > Sender: <[email protected]>; > To: zhaohuabing10201488; > CC: <[email protected]>; > Date: 2018/01/03 10:04 > Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot > repository setting?) > > > We could point to an older released version of these artifacts. > > Also, if we decide to release this newer version 1.1.0 we won't be > putting it under any particular official name like "amserdam" or > "beijing" if this is your concern. > > Thanks > Jess > > On Tue Jan 02 03:04:23 2018, [email protected] wrote: > > Hi Jess, > > > > > > 1.1.0 is just a snapshot version right now, so it should not be > > released at this point. Do we have a workaround for this issue? > > > > > > Thanks, > > > > > > Huabing > > > > > > > > > > > > > > > > > > > > > > > > Original Mail > > > > > > > > Sender: <[email protected]>; > > To: zhaohuabing10201488; > > CC: <[email protected]>; > > Date: 2017/12/30 02:12 > > Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot > > repository setting?) > > > > > > Dear Huabing, > > > > This is the last released version we had for these binaries: > > https://nexus.onap.org/content/repositories/releases/org/onap/msb/apigateway/apiroute/apiroute- > > standalone/ > > > > Looks like we need to make a release for version 1.1.0. Do you have a > > candidate for this version that we can release? > > > > Thanks! > > Jess. > > > > On Tue Dec 26 04:17:29 2017, [email protected] wrote: > > > Dear ONAP helpdesk, > > > > > > > > > > > > > > > > > > > > > I noticed that some of the jenkins jobs are continually failing, it > > > seems that the snapshot repository is missing in the ONAP maven > > > setting. > > > > > > > > > > > > > > > > > > > > > One failed Jenkins job: https://jenkins.onap.org/view/msb/job/msb- > > > apigateway-master-stage-site-java/ > > > > > > > > > > > > > > > > > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site- > > > plugin:3.6:site (default-cli) on project msb-apigateway-parent: > > > failed > > > to get report for org.apache.maven.plugins:maven-javadoc-plugin: > > > Failed to execute goal on project apiroute-standalone: Could not > > > resolve dependencies for project > > > org.onap.msb.apigateway.apiroute:apiroute-standalone:pom:1.1.0: > > > Could > > > not find artifact org.onap.msb.apigateway.apiroute:apiroute- > > > service:jar:1.1.0 in releases > > > (https://nexus.onap.org/content/repositories/releases/) -> [Help > > > 1]13:15:21 [ERROR] > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Huabing _______________________________________________ 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
