Re: [PATCH 08/10] pc-bios: refresh edk2 build artifacts for edk2-stable202008

["Philippe Mathieu-Daudé" <philmd@redhat.com>]

+Michael & Bruce

On 9/14/20 11:54 AM, Gerd Hoffmann wrote:
>   Hi,
> 
>> The CI idea is to have reproducible builds if possible.
>> When the submodule is updated (or the QEMU scripts containing the
>> -D defines), it triggers the 'build-edk2' job which produce these
>> same binaries.
>> My original idea was to push the tag on GitLab that triggers the
>> job, then download the produced binaries, test them, then commit
>> them.
> 
> Now with CI in place we maybe should step back and have a look at the
> big picture.
> 
> Should we simply stop committing firmware binaries into git and provide
> them as CI artifacts instead?

What I'm not sure about is how to keep the built artifacts forever.
Usually git-forge based projects keep release builds forever.
In our case we are interested in updating them during the development
window, to be well tested on release.

Also we need to modify the source tarball generator script to fetch
the artifacts and include them, isn't it?

>  Can we build all our firmware in CI,
> using the shared gitlab x86 runners and cross compilers?

I'm pretty sure. In case something is missing, adding it shouldn't
be a problem anyway.

Regards,

Phil.