From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8D578A053B for ; Fri, 17 Jul 2020 15:24:13 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 5B6571C127; Fri, 17 Jul 2020 15:24:13 +0200 (CEST) Received: from us-smtp-1.mimecast.com (us-smtp-1.mimecast.com [205.139.110.61]) by dpdk.org (Postfix) with ESMTP id 0E9471C126 for ; Fri, 17 Jul 2020 15:24:11 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1594992251; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=GLavxSeCb8HlGdrFdn9lbBSmHMWQCtG3TSlU6Wwj1c8=; b=H2w+CfcptdWV15D9uYnQeNo9jKoObJlkOAR7HjNawyYl779ZvRpwZMliGxFzzneHLBjr9P zn854kozQR5K5PP4E0nVv2468UhO2cFEXiTIaT5NTcMHny1qAR7DTsXMFY/rxgEbCvR2FQ icwnBuKx8DQTpCSdYQNsW669vk5jT34= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-10-GOZb-S5rNCGM9rThWyfY_g-1; Fri, 17 Jul 2020 09:24:06 -0400 X-MC-Unique: GOZb-S5rNCGM9rThWyfY_g-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A75A91080; Fri, 17 Jul 2020 13:24:04 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (ovpn-117-20.rdu2.redhat.com [10.10.117.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 924796FEF8; Fri, 17 Jul 2020 13:24:03 +0000 (UTC) From: Aaron Conole To: Juraj =?utf-8?Q?Linke=C5=A1?= Cc: "ci\@dpdk.org" References: <3f8ace7066ff499ea2982201f1329817@pantheon.tech> <65dd0476a54b4252834a129cf0942d1a@pantheon.tech> <3f5158d0761e42b8bba02d2223a7d74f@pantheon.tech> <73bd99e112d74c1fa5e60872a27ce62e@pantheon.tech> Date: Fri, 17 Jul 2020 09:24:02 -0400 In-Reply-To: <73bd99e112d74c1fa5e60872a27ce62e@pantheon.tech> ("Juraj \=\?utf-8\?Q\?Linke\=C5\=A1\=22's\?\= message of "Fri, 17 Jul 2020 07:05:51 +0000") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-ci] OBS pull request in pw-ci X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" Juraj Linke=C5=A1 writes: > Hi Aaron, > > By community maintained I meant that it's not solely on one person's > shoulders - that is, if need be, someone else (from the community) > would also be able to do the maintenance work. Ahh - yes, David Marchand has access to those servers. > Juraj > >> -----Original Message----- >> From: Aaron Conole >> Sent: Thursday, July 16, 2020 2:54 PM >> To: Juraj Linke=C5=A1 >> Cc: ci@dpdk.org >> Subject: Re: OBS pull request in pw-ci >>=20 >> Juraj Linke=C5=A1 writes: >>=20 >> > Hi Aaron, >> > >> > The dpdk community decided that the best place to maintaing the .spec >> > and .control files would be in an OBS repository. Luca is currently >> > doing that so that's where it comes from. As to how to update it - I >> > included the exact string "home:bluca:dpdk" so that it's clear we want >> > to use this repo, but it should be handled the same way as >> > UPLOAD_GIT_REPO. I didn't see how this is supplied from the code in >> > pw-ci, so I assumed it's something that's changed locally. I followed >> > the same logic for OBS_SOURCE_PACKAGE and OBS_GIT_URL - the values >> > that are there are what we should be using for our use case at this >> > point in time. >> > >> > I have a minor question about the pw-ci repo - is this your personal >> > repo (i.e. not maintained by dpdk community)? >>=20 >> I maintain it - but it's publicly accessible / available. I don't know = what else it >> means. >>=20 >> > One last thing - we'll talk today about setting up a community OBS >> > project (to mirror https://travis-ci.com/github/ovsrobot/dpdk - is >> > this actually managed by the community?) in the CI call. >>=20 >> Again, I maintain it - but it's for the community. Actually the service= that runs >> the robot is a Red Hat server, but we choose to push it to a public gith= ub and use >> a public CI so that it is all part of the community. >>=20 >> I don't know what it means to be community maintained ;) >>=20 >> > Thanks, >> > Juraj >> > >> >> -----Original Message----- >> >> From: Aaron Conole >> >> Sent: Wednesday, July 15, 2020 9:14 PM >> >> To: Juraj Linke=C5=A1 >> >> Cc: ci@dpdk.org >> >> Subject: Re: OBS pull request in pw-ci >> >> >> >> Aaron Conole writes: >> >> >> >> > Juraj Linke=C5=A1 writes: >> >> > >> >> >> Hi Aaron, >> >> >> >> >> >> Have you had a chance to look at the pull request? >> >> > >> >> > Only a bit. I will do something more thorough on Wednesday. >> >> >> >> I looked through it and it seems okay. I'll set it up to do a test >> >> run tomorrow, and merge it once that goes well. >> >> >> >> If the obs source project changes (right now, it's set to >> >> home:bluca:dpdk) how should we update it? Meaning, where does that >> >> variable come from (and if the robot needs to provide one at some >> >> point ever, how can we do that)? >> >> >> >> >> Thanks, >> >> >> Juraj >> >> >> >> >> >>> -----Original Message----- >> >> >>> From: Aaron Conole >> >> >>> Sent: Monday, July 6, 2020 7:32 PM >> >> >>> To: Juraj Linke=C5=A1 >> >> >>> Cc: ci@dpdk.org >> >> >>> Subject: Re: OBS pull request in pw-ci >> >> >>> >> >> >>> Juraj Linke=C5=A1 writes: >> >> >>> >> >> >>> > Hi folks, >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > I've submitted a PR with OBS changes to pw-ci: >> >> >>> > https://github.com/orgcandman/pw-ci/pull/12 >> >> >>> >> >> >>> Cool! I'll take a look. I was on PTO, so didn't get a chance ye= t. >> >> >>> >> >> >>> > >> >> >>> > >> >> >>> > I have a couple of points/questions: >> >> >>> > >> >> >>> > =C2=B7 The scripts are using >> >> >>> https://build.opensuse.org/package/show/home:bluca:dpdk/dpdk to >> >> >>> fork the debian and >> >> >>> > redhat spec and control files. >> >> >>> >> >> >>> Okay. A quick look shows that it's configurable, though. Should >> >> >>> be okay. I refer >> >> >>> to: >> >> >>> >> >> >>> https://github.com/orgcandman/pw- >> >> >>> >> ci/pull/12/commits/93f6baa497c85d7aca36cda6661e90f7a69d4709#diff- >> >> >>> e2ab32f32889186bdeb0ab4f0ef55282 >> >> >>> >> >> >>> > =C2=B7 We should create a community OBS project (that th= e community >> can >> >> >>> manage) where the forked packages will be >> >> >>> > created and where the build will run (OBS_TARGET_PROJECT in >> >> >>> > 3rd-party/dpdk/jenkins-rc) >> >> >>> >> >> >>> Okay. >> >> >>> >> >> >>> > o The project should be configured according to what we want = to >> build - >> >> >>> distros/architectures. Can be done via OBS GUI. >> >> >>> > >> >> >>> > =C2=B7 Only after all patches have been submitted to a s= eries branch does >> >> the >> >> >>> DPDK Jenkins job upload and configure an OBS >> >> >>> > package. This means that we'll have a build just for the whole >> >> >>> > series, not for >> >> >>> each patch. Not sure if this is a problem. >> >> >>> >> >> >>> The flip side is the amount of time to build. We'd prefer to >> >> >>> build just one at a time. >> >> >>> >> >> >>> > =C2=B7 One thing that doesn't make sense to me is that t= he DPDK Jenkins >> job >> >> >>> builds dpdk after each patch - is this needed, >> >> >>> > since Travis is going to do the same thing anyway? >> >> >>> >> >> >>> Travis doesn't. The ovsrobot travis build is configured to >> >> >>> cancel a build on a branch if a new one comes. That way we only >> >> >>> build the latest. Builds on travis take 40+ min to complete, so >> >> >>> if a 20-patch series came in, we wouldn't be done building it for >> >> >>> more than half a day. Then if a v2+ is posted in rapid >> >> >>> succession, we lost all this time. So for now, we only build the >> >> >>> absolute last patch in the series on >> >> Travis. >> >> >>> >> >> >>> Also, the build server we run the robot on doesn't do the builds >> >> >>> anymore because it also got overloaded - so meson and ninja are >> >> >>> not the actual meson/ninja but just dummy commands. :-/ Maybe I >> >> >>> should re-enable and see if things improved. >> >> >>> >> >> >>> > =C2=B7 I've added some more comments to the PR itself. >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > Regards, >> >> >>> > >> >> >>> > Juraj >> >> >>> >> >> >>=20