c8e67939 | 01-Jul-2020 |
Alex Bennée <alex.bennee@linaro.org> |
containers.yml: build with docker.py tooling
Instead of building the docker files directly use the same docker.py scripting as we do for building locally. This should help ensure we use the exact sa
containers.yml: build with docker.py tooling
Instead of building the docker files directly use the same docker.py scripting as we do for building locally. This should help ensure we use the exact same steps and allow us to cache properly when building locally.
To get this working you have to have a fairly recent docker binary otherwise you will see the error message:
=> ERROR importing cache manifest from registry.gitlab....
So far docker 19.03.12 works (from the docker apt repos) but 18.09.1, build 4c52b90 which is packaged in Debian Buster fails.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20200701135652.1366-39-alex.bennee@linaro.org>
show more ...
|
f2c5466c | 01-Jul-2020 |
Alex Bennée <alex.bennee@linaro.org> |
gitlab: limit re-builds of the containers
Most of the time we are just rebuilding the same things. We can skip this although currently there is no mechanism for picking up new distro releases.
Rath
gitlab: limit re-builds of the containers
Most of the time we are just rebuilding the same things. We can skip this although currently there is no mechanism for picking up new distro releases.
Rather than try to be too fine grained allow any change to trigger all the images being rebuilt.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20200701135652.1366-38-alex.bennee@linaro.org>
show more ...
|
8a8a50a9 | 01-Jul-2020 |
Alex Bennée <alex.bennee@linaro.org> |
gitlab: build containers with buildkit and metadata
According to the documentation to be able to use --cache-from for remote registries you need to enable both buildkit and inline the metadata. We w
gitlab: build containers with buildkit and metadata
According to the documentation to be able to use --cache-from for remote registries you need to enable both buildkit and inline the metadata. We want to do this to support pulling from gitlab when users build their local docker images.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20200701135652.1366-24-alex.bennee@linaro.org>
show more ...
|
fa821f23 | 01-Jul-2020 |
Daniel P. Berrangé <berrange@redhat.com> |
gitlab: build all container images during CI
We have a number of container images in tests/docker/dockerfiles that are intended to provide well defined environments for doing test builds. We want ou
gitlab: build all container images during CI
We have a number of container images in tests/docker/dockerfiles that are intended to provide well defined environments for doing test builds. We want our CI system to use these containers too.
This introduces builds of all of them as the first stage in the CI, so that the built containers are available for later build jobs. The containers are setup to use the GitLab container registry as the cache, so we only pay the penalty of the full build when the dockerfiles change. The main qemu-project/qemu repo is used as a second cache, so that users forking QEMU will see a fast turnaround time on their CI jobs.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Message-Id: <20200622153318.751107-3-berrange@redhat.com> [AJB: tweak the tag format] Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Acked-by: Thomas Huth <thuth@redhat.com> Message-Id: <20200701135652.1366-22-alex.bennee@linaro.org>
show more ...
|
d0caa0a8 | 01-Jul-2020 |
Daniel P. Berrangé <berrange@redhat.com> |
gitlab: introduce explicit "container" and "build" stages
If no stage is listed, jobs get put in an implicit "test" stage. Some jobs which create container images to be used by later stages are curr
gitlab: introduce explicit "container" and "build" stages
If no stage is listed, jobs get put in an implicit "test" stage. Some jobs which create container images to be used by later stages are currently listed as in a "build" stages.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Acked-by: Laszlo Ersek <lersek@redhat.com> Signed-off-by: Alex Bennée <alex.bennee@linaro.org> Reviewed-by: Thomas Huth <thuth@redhat.com> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com> Message-Id: <20200622153318.751107-2-berrange@redhat.com> Message-Id: <20200701135652.1366-21-alex.bennee@linaro.org>
show more ...
|