public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/4] CI improvements
Date: Thu, 14 Feb 2019 17:08:03 +0100	[thread overview]
Message-ID: <20190214160807.31948-1-mosipov@ilbers.de> (raw)

Hello everybody,

At the moment there is a confusion regarding CI build.
"Fast" CI build (called with parameter '-f') _cross_ builds 
3 most common (at least we think that) configurations
with cached base repository feature enabled:

 * multiconfig:qemuarm-stretch:isar-image-base
 * multiconfig:qemuarm64-stretch:isar-image-base
 * multiconfig:qemuamd64-stretch:isar-image-base

When default (w/o parameters) CI is called it _natively_ builds 
the following set of configurations:

 * multiconfig:qemuarm-jessie:isar-image-base
 * multiconfig:qemuarm-stretch:isar-image-base 
 * multiconfig:qemuarm-buster:isar-image-base
 * multiconfig:qemuarm64-stretch:isar-image-base
 * multiconfig:qemui386-jessie:isar-image-base
 * multiconfig:qemui386-stretch:isar-image-base
 * multiconfig:qemui386-buster:isar-image-base
 * multiconfig:qemuamd64-jessie:isar-image-base
 * multiconfig:qemuamd64-stretch:isar-image-base
 * multiconfig:qemuamd64-buster:isar-image-base
 * multiconfig:qemuamd64-buster-tgz:isar-image-base
 * multiconfig:rpi-jessie:isar-image-base

Unfortunately this set doesn't include supported configurations 
(real boards) 
 * multiconfig:bananapi-stretch.conf
 * hikey-stretch.conf
 * de0-nano-soc-stretch.conf

The reason is that these configurations include build of Linux kernel/U-Boot so 
the native build will last huge amount of time.

So the problem with two flavours (fast and default) of CI build is that they 
test different features for the subset of all supported configurations.

After upgrade of CI server we intend to increase a test coverage - 
 * Include cross builds for mentioned boards hikey, de0-nano-soc etc.
 * To use default build for overnight builds with different combination of features enabled 
 (native and cross, with or without used cached base repo etc.)

This patchset is the first step towards this direction.

Kind regards,
Maxim.


Maxim Yu. Osipov (4):
  ci: Introduce TARGETS_SET variable
  ci: Introduce --repro parameter to enable use of cached base
    repository
  ci: Include de0-nano-soc target into fast build
  ci: Disable use of cached base repository for fast build by default

 scripts/ci_build.sh | 71 +++++++++++++++++++++++++++++++----------------------
 1 file changed, 41 insertions(+), 30 deletions(-)

-- 
2.11.0


             reply	other threads:[~2019-02-14 16:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14 16:08 Maxim Yu. Osipov [this message]
2019-02-14 16:08 ` [PATCH 1/4] ci: Introduce TARGETS_SET variable Maxim Yu. Osipov
2019-02-14 16:08 ` [PATCH 2/4] ci: Introduce --repro parameter to enable use of cached base repository Maxim Yu. Osipov
2019-02-14 16:08 ` [PATCH 3/4] ci: Include de0-nano-soc target into fast build Maxim Yu. Osipov
2019-02-15  7:20   ` Jan Kiszka
2019-02-18  8:59     ` Claudius Heine
2019-02-18 10:18     ` Henning Schild
2019-02-18 10:23       ` Jan Kiszka
2019-02-18 10:29       ` Claudius Heine
2019-02-14 16:08 ` [PATCH 4/4] ci: Disable use of cached base repository for fast build by default Maxim Yu. Osipov
2019-02-15 14:42 ` [PATCH 0/4] CI improvements Maxim Yu. Osipov

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=20190214160807.31948-1-mosipov@ilbers.de \
    --to=mosipov@ilbers.de \
    --cc=isar-users@googlegroups.com \
    /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