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? Can we build all our firmware in CI, using the shared gitlab x86 runners and cross compilers? take care, Gerd