From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Maxim Yu. Osipov" <mosipov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: CI tests procedure
Date: Thu, 25 Apr 2019 11:30:38 +0200 [thread overview]
Message-ID: <ac98a9c6-2566-c7e9-5a83-c1b435c5a579@siemens.com> (raw)
In-Reply-To: <136d22ad-cf57-e84b-4d0d-8bb7d0e40713@ilbers.de>
On 25/04/2019 10.25, Maxim Yu. Osipov wrote:
> Hi everybody,
>
> I see that there is a misunderstanding regarding CI test procedure.
What is described here is *a* test procedure using the CI scripts, not
one implemented in the CI. Since CI just runs either "fast" or
"standard" hidden in some invisible jenkins configuration.
Claudius
>
> CI tests procedure is described in section Development of
> CONTRIBUTING.md (https://github.com/ilbers/isar/blob/next/CONTRIBUTING.md)
>
>> 3. Test your code.
>>
>> * No regressions are introduced in the affected code.
>>
>> * Seemingly unaffected boards still build.
>>
>> * It's highly suggested to test your patchset before submitting it
>> to the mailing
>> by launching CI tests scripts. The procedure is described below:
>>
>> First, run "fast" CI
>> ```
>> scripts/ci_build.sh -q -f
>> ...
>> source isar-init-build-env
>> scripts/vm_smoke_test -f
>> ```
>> Currently "fast" CI launches
>> * parallel cross build of QEMU arm/arm64/amd64 Debian stretch and
>> Raspberry Pi 1 Raspbian stretch targets
>> * cross build of one of the supported boards which includes
>> compilation of Linux kernel/U-Boot for it
>> * Launches login prompt check tests for built QEMU targets
>>
>> Second, run standard CI
>> ```
>> scripts/ci_build.sh -q
>> ...
>> source isar-init-build-env
>> scripts/vm_smoke_test -q
>> ```
>> Currently standard CI launches
>> * parallel native build of QEMU arm/arm64/i386/amd64 Debian
>> stretch/buster and Raspberry Pi 1 Raspbian stretch targets
>> * Launches login prompt check tests for built QEMU targets
>>
>> Active developers may request from maintainers an account on
>> isar-build.org
>> to analyze CI logs or to launch their own CI builds there.
>>
>>
>
> I hope, this paragraph eliminates further misunderstanding.
>
> You may send patchsets not fully tested.
> But patch set will be applied only if it passes the procedure above.
>
> Anyway I encourage you to follow this procedure to avoid patchsets
> iterations.
>
> Regards,
> Maxim.
>
--
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
prev parent reply other threads:[~2019-04-25 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 8:25 Maxim Yu. Osipov
2019-04-25 9:30 ` Claudius Heine [this message]
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=ac98a9c6-2566-c7e9-5a83-c1b435c5a579@siemens.com \
--to=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=mosipov@ilbers.de \
/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