Re: [DISCUSSIONS] CI build

[Henning Schild <henning.schild@siemens.com>]

Am Wed, 22 May 2019 09:26:51 +0200
schrieb "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>:

> 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 

Agreed, i stopped running the tests locally because i could never come
up with the same errors. Actually the CI itself could never come up
with the same ones .... but it kept failing without giving a real clue
why.
 
>   - 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

When i use the CI system from Ilbers i usually carry around a few "fast
CI" patches on top of my real changes. In there i configure CI to do
what i want and only build one config to start with. Not elegant but
works somehow.

Henning

>   - 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
>