Hi Lusheng,
I currently see a 1.1.3 in docker.snapshot repo. Ok to bump the docker
manifest to 1.1.3?
Thanks,
Gary
-Original Message-
From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Wednesday, May 30, 2018 11:21 AM
To: Gary Wu ; UNNAVA, SUNIL ;
Thanks Sunil.
Can someone from DCAE help with the other missing image?
16:04:14 [ERROR] onap/org.onap.dcaegen2.deployments.bootstrap:1.1.2 not found
Thanks,
Gary
-Original Message-
From: UNNAVA, SUNIL [mailto:su6...@att.com]
Sent: Wednesday, May 30, 2018 10:45 AM
To:
I think some teams managed to produce "release-like" tags and put them into the
docker.snapshots repo, but they were not really released via LF.
You can look up the past errors by browsing the build history for
http://12.234.32.117/jenkins/job/nexus3-docker-image-check/.
Some of the past ones
Not that I'm aware of, because virtually none of the images in the manifest are
release versions yet.
Thanks,
Gary
-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Friday, May 18, 2018 4:07 PM
To: Gary Wu
Cc:
This job runs hourly, and checks the image tags in the docker manifest:
https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv
Thanks,
Gary
-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent:
Hi Seshu,
Thanks for taking care of this. I hope LF can figure out why these docker
images keep disappearing.
Thanks,
Gary
From: Seshu m
Sent: Friday, May 18, 2018 12:23 AM
To: Gary Wu ; helpd...@onap.org;
onap-discuss@lists.onap.org
Subject: RE: [so] mso:1.2.1 image
I see that those images have re-appeared now. Not sure what happened.
Thanks,
Gary
-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Wednesday, May 09, 2018 2:16 PM
To: Gary Wu
Cc: onap-discuss@lists.onap.org
I've just added a script that will update the OOM helm charts using the
versions from the docker-manifest.csv. Going forward, teams should only need
to update the manifest as the "single source of truth", and we'll sync the OOM
and HEAT docker image versions from there.
Thanks,
Gary
Just curious, did you identify what the problem was?
Thanks,
Gary
-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Wednesday, March 07, 2018 7:38 PM
To: Gary Wu
Cc: onap-discuss@lists.onap.org
Subject: [ONAP
uijing@intel.com;
victor.mora...@intel.com
Subject: Re: [ONAP Helpdesk #50852] RE: [onap-discuss] maven artifacts
On 01/09/2018 06:34 AM, Gary Wu via RT wrote:
>
> Tue Jan 09 09:34:10 2018: Request 50852 was acted upon.
> Transaction: Ticket created by gary.i...@huawei.com
>Qu
ifacts. 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 release.
Pam
On 11/9/17, 3:12 PM, "onap-discuss-boun...@lists.onap.org on behalf of Gary Wu
vi
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:
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 Seshu,
The issue on so-master-docker-version-java-daily is due to SNAPSHOT
dependencies which are no longer allowed for staging/release builds. Please
update your pom files to replace your SNAPSHOT dependencies with Release
dependencies per the
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 thought that this in fact had already been implemented (the
capitalization-sensitive check for "Issue-ID").
Thanks,
Gary
-Original Message-
From: Kenny Paul via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Sunday, October 22, 2017 7:51 PM
To: Gary Wu
realized the same issue today, we too had opened
> below ticket to LF, earlier to this email.
>
> “[linuxfoundation.org #46449] Portal/SDK jars missing from nexus maven
> staging repository”
>
> Manoop
>
>
> On 10/18/17, 11:15 AM, "onap-discuss-boun...@lists.onap.
Hold on… it looks like all autorelease directories older than last Friday got
removed, which is a big issue for multiple teams. Catherine will be escalating
for a restore.
Thanks,
Gary
From: Gary Wu
Sent: Wednesday, October 18, 2017 8:05 AM
To: 'zhao.huab...@zte.com.cn'
The directory autorelease-18453 doesn’t seem to exist on nexus right now.
Maybe the autorelease directories get removed after a certain time?
You’ll need to re-run the staging (-release-version-*) jobs to build to
staging/autorelease again. After that, if the result is good, please email LF
Hi Kishore,
I tried to to run your test suite in my local machine, and it also failed.
The error is:
02:10:35 ++ mkdir -p /PROJECT/OpenSource/UbuntuEP/etc
02:10:35 mkdir: cannot create directory ‘/PROJECT’: Permission denied
The same error was also observed on the LF CSIT environment.
I
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
Looks like the docker image now builds fine on LF infrastructure, but the job
is failing because the existing "docker push" script is hardcoded to assume
"openecomp/" as the image name prefix instead of "onap/".
We'll probably need some refactoring for a more generic docker build job
template
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
Hi Kanagaraj,
There are unfortunately two different docker-maven-plugins in use in ONAP: one
from io.fabric8, one from com.spotify.
The one that you’re using is from spotify, which needs a different JJB template
for the docker job.
I’ve submitted a change to your CLI JJB file which changes it
Hi Kanagaraj,
I've submitted a change to CLI that should fix the issue. Please review/merge.
https://gerrit.onap.org/r/#/c/8507/
Thanks,
Gary
-Original Message-
From: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Jessica Wagantall via
Hi Murali,
The latest run of that job has completed successfully now, I think because of
your fix in https://gerrit.onap.org/r/#/c/8271/.
Thanks,
Gary
From: Murali p
Sent: Tuesday, August 22, 2017 4:51 AM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org; 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,
: [ONAP Helpdesk #44125] Independent project artifact release process
Greetings Gary,
On 08/16/2017 11:34 AM, Gary Wu via RT wrote:
> Resending since I didn't get a ticket number back for some reason last time.
Not certain why you didn't. The original ticket, which I've merged this into is
441
I think it may have something to do with whatever Andy fixed this morning.
I've copied the email thread below.
Thanks,
Gary
-
Greetings folks,
I saw an error this morning related to this. It should now be resolved.
-Andy-
On 08/14/2017 07:31 AM, WONNELL, SKIP wrote:
> Yes, I see the
Hi Jessica,
It seems to be working now.
Thanks,
Gary
-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Monday, August 14, 2017 1:20 PM
To: Gary Wu
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #44073]
cript for python project in ONAP
Gary's changes have been merged in and the redis image has been built.
I've added a new minion template to allow the image to come online.
-Andy-
On 08/10/2017 09:55 AM, Gary Wu via RT wrote:
>
> Sorry about that. I’ve submitted a fix into ci-management:
&
Sorry about that. I’ve submitted a fix into ci-management:
https://gerrit.onap.org/r/#/c/7229/
Thanks,
Gary
From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn]
Sent: Wednesday, August 09, 2017 5:54 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: zhang.maope...@zte.com.cn; Gary Wu
Hi Jessica,
Am I supposed to be able to access that link? If not yet, can I be granted
read access?
Thanks,
Gary
-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Monday, August 07, 2017 1:57 PM
To: Gary Wu
enkins is down
On Fri Jul 21 13:21:36 2017, agrimberg wrote:
> On 07/21/2017 10:11 AM, Gary Wu via RT wrote:
>
> > Hi helpdesk,
> >
> > http://jenkins.onap.org/ is not responding. Can you take a look?
> >
> > Thanks,
> > Gary
>
> Greetings Gary,
>
&
Hi Jess,
Seems it is working again now. If you look at e.g.
https://gerrit.onap.org/r/#/c/5789/ you can see that the first couple of jobs
that got triggered did not update Gerrit, but the final "recheck" did.
Thanks,
Gary
-Original Message-
From: Jessica Wagantall via RT
36 matches
Mail list logo