: Friday, November 10, 2017 8:48 AM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo
precedence issue
Gary,
This breaks current projects whose release jobs on the master branch are
producing Staging art
: Friday, November 10, 2017 8:48 AM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo
precedence issue
Gary,
This breaks current projects whose release jobs on the master branch are
producing Staging art
Gary,
This breaks current projects whose release jobs on the master branch are
producing Staging artifacts. I will now have to remove those jobs.
I understand for a formal release process you don’t want staging in the mix.
But unfortunately perhaps this could have been done post Amsterdam
Gary,
This breaks current projects whose release jobs on the master branch are
producing Staging artifacts. I will now have to remove those jobs.
I understand for a formal release process you don’t want staging in the mix.
But unfortunately perhaps this could have been done post Amsterdam
Thanks Jess.
All teams: Please make sure that you are no longer building against staging
artifacts. If you still have dependencies on staging artifacts, please contact
the upstream teams to make sure that they formally release those artifacts.
Thanks,
Gary
-Original Message-
From:
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, gary.i...@huawei.com wrote:
> Hi Jessica,
>
> Thanks for the investigation. At this point in
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
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
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
This issue is still occurring and still needs LF resolution.
Thanks,
Gary
-Original Message-
From: Kenny Paul via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Sunday, October 22, 2017 7:43 PM
To: Gary Wu
Cc: onap-discuss@lists.onap.org
Subject: [ONAP
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, gary.i...@huawei.com wrote:
> I just noticed the issue today, but I suspect it's been happening for
> a
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-helpd...@rt.linuxfoundation.org]
Sent: Wednesday, September 06, 2017 2:10 PM
To: Gary Wu
Cc:
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-helpd...@rt.linuxfoundation.org]
Sent: Wednesday, September 06, 2017 2:10 PM
To: Gary Wu
Cc:
Actually I think the key step is the next one where "clean deploy" is being
done, but it doesn't hurt to have them all configured to have Releases be the
top priority.
Also this should really be done for all Maven jobs including merge and verify,
not just release-version.
The right long term
Actually I think the key step is the next one where "clean deploy" is being
done, but it doesn't hurt to have them all configured to have Releases be the
top priority.
Also this should really be done for all Maven jobs including merge and verify,
not just release-version.
The right long term
Hey Gary, quick question.. did you saw this happening the time we released
oparent 0.1.0?
Thanks!
Jess
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
Sure Gary,
It seems that this should be a property of this step:
versions:set versions:update-child-modules versions:commit -B
Let me investigate how to do that in this case and get back to you
Thanks!
Jess
___
onap-discuss mailing list
17 matches
Mail list logo