We seem to be close to the QEMU memory limit in GHA, that's why actions
fail sporadically.
Switch to native builds, aka build amd64 in an amd64 machine and do the
same for arm64.
This means we need to push 2 extra tags: foo-amd64 and foo-arm64 and
then create a manifest to unite them both.
Ref: https://github.com/docker/build-push-action/issues/621
This is the version we evaluate config.js with on Android, making it the
lowest common denominator. While being a nifty little engine, it suffers
from not being fully ES6 compliant, so things like arrow functions or
template strings are not implemented.
* feat(lint): add tpl lint step for each project
* fix path
* fix path
* include jicofo and jibri
* temp cat to test
* more templates to lint
* fix path
* fix jigasi password b64 default behavior
* ci: split unstable build and test workflows
In order to make multi-arch builds the buildx action will use the
docker-container driver, which does not support loading images, and thus
the jvb image won't be built based on the "base-java" image, in turn based
on the "base" image. That works only when pushing.
If we setup buildx to use the "docker" driver it will just build for the
current architecture, but it will properly load images and the base
images will be used correctly.
One downside is that jobs cannot be run in parallel, but it seems to be Fast Enough (R) for now.
