All I can offer is my experience, namely that the deploy step failed when my POM used "ecomp-snapshots":
https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/portal-sdk-master-ecomp-sdk-merge-java/12/console.log.gz And succeeded when my POM used "snapshots": https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/portal-sdk-master-ecomp-sdk-merge-java/13/console.log.gz The error log shows "ecomp-snapshots" but the success log shows no server IDs at all. Could it have been something transient? Sure, but that seems like a bit of stretch. > On Sep 5, 2017, at 3:07 PM, Jessica Wagantall via RT > <onap-helpd...@rt.linuxfoundation.org> wrote: > > Dear Gary, > > Just to confirm, we are still using ecomp-staging, ecomp-snapshots and (if > your project needs it) ecomp-site. Those are the servers that we have defined > in the Jenkins config files. The pom files can still have the ecomp-releases > block but this ServerID will no longer be accessible from the Jenkins > configuration files due to all the previous accidental pushes into the > release repo. > > I have discussed with Andy the future change to remove the "ecomp-" prefix > from the ServerIds in order to make them more generic. This is a big change > and surely will take a lot of effort. For now, if we see teams using the > generic names, I make sure the config files matches those generic names too. > > The unauthorized errors are tricky becuase it can be problems with the parent > pom.xml, the privileges, the user/pass combo, the group-id... > > Thanks! > Jess _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
