Re: [SPDK] [CI] Opening Geritt for external CI

* Re: [SPDK] [CI] Opening Geritt for external CI
@ 2018-12-03 18:25 Luse, Paul E
  0 siblings, 0 replies; 19+ messages in thread
From: Luse, Paul E @ 2018-12-03 18:25 UTC (permalink / raw)
  To: spdk

[-- Attachment #1: Type: text/plain, Size: 5570 bytes --]

Hot damn... thanks Seth! Sasha, let us know when you've got things setup, excited to see our first external CI system fired up.

Thx
Paul

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Howell, Seth
Sent: Monday, December 3, 2018 11:22 AM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] [CI] Opening Geritt for external CI

Hi Sasha,

This is great news!! We can definitely get you tied in.
Name: spdk-gerrithub
Hostname: https://review.gerrithub.io/
SSH Port: 29418
Proxy: *Determined by your configuration*
Username: *You will have to create a github user for your Jenkins instance and log it into gerrithub* SSH Keyfile: *Make sure the file you upload here is associated on gerrithub with the user you created above* We also have two checkboxes checked on the configuration page 1. Build Current Patches Only (Prevents us from running old versions of reviews through the test pool) 2. Allow Other Plugins to Contribute Messages (I will have to defer to Karol on why this is checked)

The plugin supports using either the verified flag  or the Code review flag. It would be best (especially at the outset) to use the Code-Review flags to report your test pool passing or failing.
We have ours configured to say
Successful: 1
Failed: -1

There should be no need to add additional privileges to your user to support this configuration as all users can write reviews.

Please continue to reach out as you configure your system.

Thanks,

Seth
-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Sasha Kotchubievsky
Sent: Monday, December 3, 2018 11:06 AM
To: spdk(a)lists.01.org
Subject: Re: [SPDK] [CI] Opening Geritt for external CI

Hi Karol,

We're using Jenkins with Gerrit Trigger plugin.

I'd like to have a dedicated CI user mlnx-swx-jenkins, how can we register it? Does it needs special permissions?

Thanks

Sasha

On 12/3/2018 10:36 AM, Latecki, Karol wrote:
> Hi Sasha!
>
> Could you tell us which CI system are you trying to hook up?
> We're using Jenkins with Gerrit Trigger plugin. If that's the same case for you then there should be no need to grant access to react to events on Gerrithub  - you just need to specify a user and a password to use in GerritHub.
>
> If you could share some more details on what you're trying to set up then I would be able to help more.
>
> Thanks,
> Karol
>
> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Luse, Paul 
> E
> Sent: Sunday, December 02, 2018 8:10 PM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: Re: [SPDK] [CI] Opening Geritt for external CI
>
> Hi Sasha,
>
> That's great news! Getting additional CI systems tied into GH will go 
> a long way in our continual efforts to increase SW quality. You should 
> hear back from someone by EOD Mon, I'm not sure exactly how to get you 
> hooked in but I'd like to find out myself so will dig in a bit 
> tomorrow :)
>
> Thanks!
> Paul
>
> -----Original Message-----
> From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Sasha 
> Kotchubievsky
> Sent: Sunday, December 2, 2018 2:43 AM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: [SPDK] [CI] Opening Geritt for external CI
>
> Hi,
>
> We (Mellanox)  see a big value in SPDK project and have started to invest developing effort to bring advanced HW offloads to the mostly NVME-OF area, but not limited. To support this developing effort, we're bringing up internal CI.  We would like to contribute to SPDK testing, detect and to report found issues before patch merging. For example, set “-1,1” for patches. Following discussions in SPDK Dev Meetup in October 2018, we would like to start integration between our CI and upstream Gerrit. Can you grant access for our CI for fetching patches and reporting status?
>
> Best regards
>
> Sasha
>
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
> --------------------------------------------------------------------
>
> Intel Technology Poland sp. z o.o.
> ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN.
>
> Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego 
> adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione.
> This e-mail and any attachments may contain confidential material for 
> the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

^ permalink raw reply	[flat|nested] 19+ messages in thread