From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Aaron Conole <aconole@redhat.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: [dpdk-ci] OBS pull request in pw-ci
Date: Fri, 3 Jul 2020 13:08:16 +0000 [thread overview]
Message-ID: <3f8ace7066ff499ea2982201f1329817@pantheon.tech> (raw)
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
Hi folks,
I've submitted a PR with OBS changes to pw-ci: https://github.com/orgcandman/pw-ci/pull/12
I have a couple of points/questions:
* The scripts are using https://build.opensuse.org/package/show/home:bluca:dpdk/dpdk to fork the debian and redhat spec and control files.
* We should create a community OBS project (that the 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)
o The project should be configured according to what we want to build - distros/architectures. Can be done via OBS GUI.
* Only after all patches have been submitted to a series 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.
* One thing that doesn't make sense to me is that the DPDK Jenkins job builds dpdk after each patch - is this needed, since Travis is going to do the same thing anyway?
* I've added some more comments to the PR itself.
Regards,
Juraj
[-- Attachment #2: Type: text/html, Size: 7850 bytes --]
next reply other threads:[~2020-07-03 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 13:08 Juraj Linkeš [this message]
2020-07-06 17:31 ` Aaron Conole
2020-07-13 14:20 ` Juraj Linkeš
2020-07-13 20:17 ` Aaron Conole
2020-07-15 19:13 ` Aaron Conole
2020-07-16 11:58 ` Juraj Linkeš
2020-07-16 12:54 ` Aaron Conole
2020-07-17 7:05 ` Juraj Linkeš
2020-07-17 13:24 ` Aaron Conole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f8ace7066ff499ea2982201f1329817@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).