Re: [onap-discuss] [ONAP Helpdesk #57562] Jira and Gerrit integration not reliable

[Andrew Grimberg via RT]

On 06/21/2018 02:04 PM, rx1...@att.com via RT wrote:
> Dear Helpdesk,
> 
> Can you tell me why Jira sometimes shows the Gerrit submission  and
> sometimes not. I have not been able to identify a pattern to this.
> It seems to randomly work. This is a real productivity issue when we
> can't reliably depend on Jira to show us the linked Gerrit submission
> and we have to hunt around for things in Gerrit.
> 
> Thanks, Randa

Greetings Randa,

The integration is working. The issue is that the plugin maintains a
cache of changes that it's aware of. If at anytime you are feeling that
there is something that isn't being shown then to the right of the
Gerrit header there is a pull down (down arrow) that you can toggle
between the view of the types of issues. Whenever this is done it will
_force_ the plugin to invalidate the cache and recheck for changes that
meet the linking criteria.

There is no configuration for the plugin that we can set to avoid this.
The only configuration we have is to point the plugin at a single Gerrit
instance and set the search query that is used to find linked issues.

-Andy-

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10503): https://lists.onap.org/g/onap-discuss/message/10503
Mute This Topic: https://lists.onap.org/mt/22531033/21656
Group Owner: onap-discuss+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-



bint05F23q9cu.bin
Description: application/rt-original-message

Re: [onap-discuss] [ONAP Helpdesk #50852] RE: maven artifacts

[Andrew Grimberg via RT]

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
>Queue: ONAP Helpdesk
>  Subject: RE: [onap-discuss] maven artifacts
>Owner: Nobody
>   Requestors: gary.i...@huawei.com
>   Status: new
>  Ticket https://rt.linuxfoundation.org/Ticket/Display.html?id=50852 >
> 
> 
> I’m not sure why the 1.1.0-SNAPSHOT versions disappeared again.  I wonder if 
> something is wrong with Nexus.
>
> Helpdesk, can you help?  1.1.0-SNAPSHOT used to exist here, but it has since 
> disappeared: 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicloud/openstack/multicloud-openstack-newton/
> 
> Also, there are occasions where the merge job seems to have created 
> 1.1.0-SNAPSHOT but then it’s nowhere to be found:
> https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-newton-merge-java/57/console
> 
> Thanks,
> Gary

Nothing is wrong with Nexus. There is a 1.1.0 release of this artifact
in the system [0] Nexus auto-purges SNAPSHOT copies of released
artifacts as any further development _must_ end up on a new version
since you can't release new copies of the same version. There is a grace
period of 14 days that a SNAPSHOT version will continue to exist at the
same time that there is a release version. But in this case we're way,
way, way past that window since the release version of this happened in
the middle of November (November 16, 2017 to be specific).

If you end up generating a new SNAPSHOT artifact at a version in this
state it will exist for a very, very short amount of time until the
Nexus artifact reaper comes through which happens once a day.

-Andy-

[0]
https://nexus.onap.org/content/repositories/releases/org/onap/multicloud/openstack/multicloud-openstack-newton/1.1.0/

> 
> From: Morales, Victor [mailto:victor.mora...@intel.com]
> Sent: Monday, January 08, 2018 9:43 AM
> To: Gary Wu ; Yang, Bin (Wind River) 
> ; Guo, Ruijing ; 
> onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] maven artifacts
> 
> Hey Gary,
> 
> We’re still having issues to deploy the 1.1.0-SNAPSHOT version for 
> multicloud-openstack-newton artifact [1].  The –merge-java job looks like was 
> successfully executed [2] when the version was bumped [3] but there is no 
> artifact placed for that specific version, as consequence other jobs are 
> failing [4].  I’m not sure if the deployment process needs to be done 
> separately (per subproject) [5] given that the parent pom.xml contains the 
> reference of every subproject[6]
> 
> Regards/Saludos
> Victor Morales
> 
> [1] 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicloud/openstack/multicloud-openstack-newton/
> [2] 
> https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/multicloud-openstack-master-newton-merge-java/55/console.log.gz
> [3] https://gerrit.onap.org/r/#/c/24617/
> [4] 
> https://jenkins.onap.org/job/multicloud-openstack-master-ocata-verify-java/65/
> [5] 
> https://git.onap.org/ci-management/tree/jjb/multicloud/multicloud-openstack.yaml
> [6] https://git.onap.org/multicloud/openstack/tree/pom.xml#n37
> 
> From: 
> >
>  on behalf of Gary Wu >
> Date: Thursday, December 21, 2017 at 9:58 AM
> To: "Yang, Bin (Wind River)" 
> >, "Guo, Ruijing" 
> >, 
> "onap-discuss@lists.onap.org" 
> >
> Subject: Re: [onap-discuss] maven artifacts
> 
> I’m not sure why it didn’t work before, but I just re-ran that job and now 
> the artifact is there.
> 
> Thanks,
> Gary
> 
> From: Yang, Bin [mailto:bin.y...@windriver.com]
> Sent: Wednesday, December 20, 2017 6:51 PM
> To: Gary Wu >; GUO, RUIJING 
> >; 
> onap-discuss@lists.onap.org
> Subject: RE: [onap-discuss] maven artifacts
> 
> Hi Gary,
> 
>The -merge-java job seems working well, but the snaphot 
> artifacts is nowhere to find on nexus.onap.org. Could you help look into this 
> log to find out any clue ?
> 
> https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-newton-merge-java/lastBuild/console
> 
> Thanks.
> 
> Best Regards,
> Bin Yang,Solution Readiness Team,Wind River
> Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
> Skype: yangbincs993
> 
> From: Gary Wu [mailto:gary.i...@huawei.com]
> Sent: Wednesday, December 20, 2017 3:40 PM
> To: GUO, RUIJING; 
> onap-discuss@lists.onap.org
> Cc: Yang, Bin
> 

[onap-discuss] [ONAP Helpdesk #48276] Huge Jenkins queue

[Andrew Grimberg via RT]

On Thu Nov 16 10:46:39 2017, agrimberg wrote:
> On Thu Nov 16 10:07:50 2017, jeremyphelps wrote:
> > Hi Gary,
> > We have identified the issue.  There will be a pause in the Jenkins
> > queue momentarily to sort the situation.
> > Jeremy
> >
> > On Thu Nov 16 10:01:54 2017, jeremyphelps wrote:
> > > Hi Gary,
> > > We are currently set at 40.  I'm seeing if we can increase now.
> > > Jeremy
> > >
> > > On Thu Nov 16 09:52:53 2017, gary.i...@huawei.com wrote:
> > > > Hi helpdesk,
> > > >
> > > > Currently there are almost 100 Jenkins jobs backed up as we're
> > > > ramping
> > > > up for the release.  Any way we can temporarily increase the
> > > > number
> > > > of
> > > > Jenkins slaves to help out?
> > > >
> > > > Thanks,
> > > > Gary
> 
> Please note, we are still actively working this issue. Jenkins is
> currently in shutdown mode as we are evaluating if we need to actually
> give Jenkins a restart to get an error we're seeing the logs which is
> related to it bringing build instances online to clear.
> 
> -Andy-

Greetings folks,

After poking the system some more and giving Jenkins a restart we've cleared up 
the problem with the build instances not properly connecting. We have also 
temporarily increased the maximum number of instance from 40 to 60 to better 
speed along clearing the queue.

-Andy-

-- 
Andrew Grimberg
The Linux Foundation
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #48276] Huge Jenkins queue

[Andrew Grimberg via RT]

On Thu Nov 16 10:07:50 2017, jeremyphelps wrote:
> Hi Gary,
> We have identified the issue.  There will be a pause in the Jenkins
> queue momentarily to sort the situation.
> Jeremy
> 
> On Thu Nov 16 10:01:54 2017, jeremyphelps wrote:
> > Hi Gary,
> > We are currently set at 40.  I'm seeing if we can increase now.
> > Jeremy
> >
> > On Thu Nov 16 09:52:53 2017, gary.i...@huawei.com wrote:
> > > Hi helpdesk,
> > >
> > > Currently there are almost 100 Jenkins jobs backed up as we're
> > > ramping
> > > up for the release.  Any way we can temporarily increase the number
> > > of
> > > Jenkins slaves to help out?
> > >
> > > Thanks,
> > > Gary

Please note, we are still actively working this issue. Jenkins is currently in 
shutdown mode as we are evaluating if we need to actually give Jenkins a 
restart to get an error we're seeing the logs which is related to it bringing 
build instances online to clear.

-Andy-

-- 
Andrew Grimberg
The Linux Foundation
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #44125] [integration] Independent project artifact release process

[Andrew Grimberg via RT]

On Wed Aug 16 15:26:15 2017, gary.i...@huawei.com wrote:
> Hi Andy,
> 
> Thanks for your feedback.  I would like to do a trial run of this
> process with oparent and document the instructions.
> 
> To confirm, is the preferred way to do a staging build via the "-
> release-version-java-daily" jobs?  Do we currently have any
> documentation on how to setup/use the staging build jobs?  For
> example, I think it requires a version.properties file to be defined
> in the repo; not sure if there are other requirements.

Greetings Gary,

Just circling back on this. I'm going to direct this at [0]

> For the GPG signed tag, do we have any recommended instructions for
> the project committers/PTLs to do so themselves, or should we assume
> that LFRE will take care of this for the time being?

At present LFRE will take care of this, as I'm sure you're aware of with your 
recent releases of oparent.

[0] https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process

-- 
Andrew Grimberg
The Linux Foundation
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #45935] Jenkins Sandbox Setup Issue

[Andrew Grimberg via RT]

On Tue Sep 19 12:59:55 2017, jwagantall wrote:
> - You will need to comment this lines in jjb/global-jjb/jjb/lf-
> macros.yaml and jjb/global-macros.yaml
>   - openstack:
>   single-use: true

The above should not be done. Even when using the sandbox you want your 
instance to be single use, otherwise work that you're testing in the sandbox 
can impact other folks testing work.

-Andy-

-- 
Andrew Grimberg
The Linux Foundation
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #44125] Independent project artifact release process

[Andrew Grimberg via RT]

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 44125

> From: Gary Wu
> Sent: Wednesday, August 09, 2017 12:37 PM
> To: 'helpd...@onap.org' 
> Cc: onap-discuss@lists.onap.org
> Subject: [integration] Independent project artifact release process
> 
> Hi helpdesk,
> 
> ONAP is moving toward a model where each project/repo will be
> releasing its own artifacts and versions, and cross-repo dependencies
> are on release artifacts only (i.e. no SNAPSHOT/staging dependencies).
> Integration will be piloting this with oparent and clamp repos to work
> out all the kinks.
> 
> To that end, we will need a clear process for individual projects to
> version bump and release their own artifacts.
> 
> ONAP currently has Jenkins job definitions that will deploy release
> artifact candidates to staging. What seems to be missing is a way for a
> project to pick a candidate from staging and formally release it into
> the Releases repo. Does this process exist? If so, can you point me to
> some documentation on how this process works? If not, can you share your
> thoughts on how we can best implement this last step?

The closest we currently have is the process that OpenDaylight has been
operating with for their odlparent project which as of the current
release cycle has broken off to doing independent releases of it's one.
In fact during the Nitrogen cycle it's already had at least 4 releases
that I'm aware of!

The current process that has been in use in ODL by odlparent is detailed
in the lead mail in this [0] mailing list thread.

LF is working on ways that the we can grant more of the process control
to the projects themselves but we don't currently have everything needed
for it just yet.

To get the heart of your request the current way for an ONAP project to
formally do a release at present would be as follows:

1) A staging build has happened. In the job logs there will be a notice
as to what the staging repository that was created is. This needs to be
captured by a project committer / PTL that will be requesting a release

2) Any testing that needs to be performed against the artifacts is
performed.

3) A helpdesk ticket is opened requesting that LF Release Engineering
perform a signing and release operation on the target staging repository

4) LFRE will pull the artifacts, GPG sign them, push a secondary staging
repository with the signatures and then perform a release operation
inside nexus which will cause it to transition both the requested
staging repository and the signature repository to copy into the
releases repository and then delete the staging repositories.

5) A GPG signed tag needs to be placed on the commit by either LFRE or
preferably the PTL or a committer of the project with the release version

For docker images, we don't currently have as much automated tooling in
place but the basic flow is:

1) Identify the STAGING docker slice that is to be released

2) Open a ticket with LF to release the specific docker

3) LFRE will pull the docker image and retag it into the nexus docker
releases repository and push

4) The image should also then be pushed to dockerhub

Eventually, this will all get fully automated in some fashion with the
correct checks and balances in place for restricting who can do what.
Once we have a good automation flow in place then it will probably be a
matter of an authorized party submitting a gerrit change to a special
repository / specially formatted comment to trigger Jenkins to perform
operations on behalf of folks.

-Andy-

[0] https://lists.opendaylight.org/pipermail/dev/2017-August/003990.html

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation




binrzPHcH0pRW.bin
Description: application/rt-original-message
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [linuxfoundation.org #44094] Re: [linuxfoundation.org #44094] RE: [ONAP Helpdesk #44094] 答复: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

[Andrew Grimberg via RT]

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: 
> 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 ; 
> onap-discuss@lists.onap.org
> Subject: 答复: [ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] 
> RE: About CI job Script for python project in ONAP
> 
> 
> Hi Jess,
> 
> I think Gary's script has some mistakes, you can see the following log
> 
> 18:13:06 openstack: mv: cannot stat '/tmp/redis-4.0.1/redis-server': No 
> such file or directory
> 
> Gary's Scripts(Path of redis-server and redis.conf are wrong)
> 
># 2. set conf file and init script
> 
> mv /tmp/redis-4.0.1/redis-server /etc/init.d/redis-server
> 
> chmod +x /etc/init.d/redis-server
> 
> mv /tmp/redis-4.0.1/redis.conf /etc/redis.conf
> 
> 
> 
> Thanks,
> 
> Jinhua
> 
> 
> 
> 
> 
> 
> 原始邮件
> 发件人： 
> >;
> 收件人：张茂鹏10030173;
> 抄送人：傅锦华10108953; >; 
> >;
> 日 期 ：2017年08月10日 07:01
> 主 题 ：[ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About 
> CI job Script for python project in ONAP
> 
> 
> Dear Maopeng,
> 
> I am currently working on this.
> Looking at the current failures found here:
> https://jenkins.onap.org/job/ci-management-merge-packer-ubuntu-16.04-redis/1/console
> 
> Will let you know once I get this resolved
> 
> Thanks!
> Jess
> 
> 
> 
> 
> 

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation




bin0XKCAnBr98.bin
Description: application/rt-original-message
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [linuxfoundation.org #44058] Re: [ONAP Helpdesk #44058] RE: RE: RE: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

[Andrew Grimberg via RT]

On 08/08/2017 07:17 AM, Gary Wu via RT wrote:
> Hi helpdesk,
> 
> Can you help?  It seems that the redis minion is unavailable in Jenkins.
> 
> Thanks,
> Gary

While the template has been merged, the ci-management job set that
creates the packer image still needs to be updated. After the job is
updated and the image built there is a manual process that LF Release
Engineering must do to update any Jenkins minion definitions to make use
of the new images. This is true for updates to current images as well.

This means that there are still several steps needed to be performed
before the image is available.

-Andy-

> From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn]
> Sent: Monday, August 07, 2017 8:01 PM
> To: Gary Wu 
> Cc: onap-discuss@lists.onap.org
> Subject: 答复: RE: RE: Re:[onap-discuss] 答复: [integration] RE: About CI job 
> Script for python project in ONAP
> 
> 
> Hi Gary,
> 
> I found that your commit for redis install in jenkins env has merged, and I 
> modify the job node to ‘ubuntu1604-redis-4c-4g’,
> 
> but jenkins shows that node  ‘ubuntu1604-redis-4c-4g’ can not be found, can 
> you check it again?
> 
> Thanks,
> 
> Jinhua

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation




binOoKTu5QowL.bin
Description: application/rt-original-message
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss