public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: [DISCUSSIONS] CI build
Date: Wed, 22 May 2019 09:26:51 +0200	[thread overview]
Message-ID: <b5c9fb55-5d59-8be4-ccdd-d6fd45edda76@siemens.com> (raw)

Hi,

we discussed some issues with the CI offline.

Here are my issues of the current CI with Jenkins in text:
  - Unreliable build:
    -> Network and other unrelated issues to the patch
    -> Contains expected to fail tests
  - Not transparent configuration/environment:
    -> parameters with which ci_build.sh is called are not controllable 
from the repository
    -> difficult to select which test case should be run
    -> Configuration of the environment is not controllable from the 
repository: Installed packages, System configuration (locales), 
Distribution, etc.
  - Just one giant build process
    -> Takes a long time
    -> Cannot be spread over multiple servers
    -> Giant log file, that makes it difficult to figure out exactly 
which command or test case caused an issue to reproduce that locally
  - Manually triggering of build jobs
    -> After pushing of CI branch, build has to be triggered via button
    -> Patches on ML should be automatically tested and reported back to 
ML (that only makes sense if the build is reliable though)
  - No "test everything" (acceptance test) build job
  - Logs aren't public accessible

Anyone has other issues or comments?

regards,
Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

             reply	other threads:[~2019-05-22  7:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22  7:26 Claudius Heine [this message]
2019-05-22  8:20 ` Maxim Yu. Osipov
2019-05-22  9:10   ` Claudius Heine
2019-05-22  9:50     ` Maxim Yu. Osipov
2019-05-22 11:28       ` Claudius Heine
2019-05-23  8:10         ` Claudius Heine
2019-05-23 13:43           ` Claudius Heine
2019-05-23 13:56             ` Maxim Yu. Osipov
2019-05-23 14:36               ` Claudius Heine
2019-05-22 19:44 ` Baurzhan Ismagulov
2019-05-23  4:44   ` Jan Kiszka
2019-05-23  8:32     ` Claudius Heine
2019-05-23  8:39       ` Jan Kiszka
2019-05-23 10:58       ` Maxim Yu. Osipov
2019-05-23 11:35 ` Henning Schild
2019-05-23 12:11   ` Baurzhan Ismagulov
2019-05-30  8:29 ` Jenkins project configuration by user 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=b5c9fb55-5d59-8be4-ccdd-d6fd45edda76@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --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