Dear Gary, We have now removed the staging as an active profile from global-settings.xml now and the dependencies should now be downloaded from releases.
Thanks! Jess On Mon Nov 06 13:43:31 2017, [email protected] wrote: > Hi Jessica, > > Thanks for the investigation. At this point in the release cycle, I > think the better solution now is to just completely remove staging > from settings.xml. All teams should be formally releasing their > artifacts by now, and we should no longer be having any build > dependencies on staging artifacts. This would completely eliminate > the precedence issue. > > Thanks, > Gary > > -----Original Message----- > From: Jessica Wagantall via RT [mailto:onap- > [email protected]] > Sent: Friday, November 03, 2017 6:21 PM > To: Gary Wu <[email protected]> > Cc: [email protected] > Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence > issue > > Dear Gary, > > I was briefly talking with Andy about this ticket. > > I made a test in the sandbox in where I am changing the values that > global-settings have as the active profiles. Basically, this file has > the releases, staging, snapshot active profiles described in that > order. This file controls the precedence of the repos where is going > to do the downloads. > > Here is a run on the job with that described global settings: > https://jenkins.onap.org/sandbox/job/integration-master-version- > manifest-release-version-java-daily/2/console > This job downloaded the release version of oparent: 00:53:19 [INFO] > Downloaded: > https://nexus.onap.org/content/repositories/releases/org/onap/oparent/oparent/0.1.1/oparent- > 0.1.1.pom (21 KB at 430.4 KB/sec) > > I did a small test in which I removed the releases profile and the > download happened from the public repo: > https://jenkins.onap.org/sandbox/job/integration-master-version- > manifest-release-version-java-daily/6/console > > Another thing that Andy mentioned, is that whenever this download > fails, the log will report the last place where it looked for the > binaries. For example, if we ask the job to look into releases and > then staging, if it fails it will report the failure while looking > into staging making the log look like it didn't looked in releases > even though it actually did. It just happens that maven will report > the failure making reference to the last profile it looked into. > > Let me know if you would like to make more tests with my setup, I can > place the jobs in the Sandbox for us to experiment more. > > Thanks! > Jess > > On Tue Oct 24 00:29:23 2017, [email protected] wrote: > > This issue is still occurring and still needs LF resolution. > > > > Thanks, > > Gary > > > > -----Original Message----- > > From: Kenny Paul via RT [mailto:onap- > > [email protected]] > > Sent: Sunday, October 22, 2017 7:43 PM > > To: Gary Wu <[email protected]> > > Cc: [email protected] > > Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence > > issue > > > > I’m reviewing all of the tickets in the LF IT queue that are open. > > Is this still an issue that needs support from IT or can this ticket > > be closed? > > > > Thanks! > > -kenny > > > > On Wed Sep 06 17:18:23 2017, [email protected] wrote: > > > I just noticed the issue today, but I suspect it's been happening > > > for a long time. > > > > > > Thanks, > > > Gary > > > > > > -----Original Message----- > > > From: Jessica Wagantall via RT [mailto:onap- > > > [email protected]] > > > Sent: Wednesday, September 06, 2017 2:10 PM > > > To: Gary Wu <[email protected]> > > > Cc: [email protected] > > > Subject: [ONAP Helpdesk #45447] [integration] Maven repo > > > precedence > > > issue > > > > > > Hey Gary, quick question.. did you saw this happening the time we > > > released oparent 0.1.0? > > > > > > Thanks! > > > Jess > > > > > > > > > _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
