CI tests procedure

CI tests procedure

[Maxim Yu. Osipov]

Hi everybody,

I see that there is a misunderstanding regarding CI test procedure.

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.

-- 
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov

Re: CI tests procedure

[Claudius Heine]

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