Turned out that linaro-london network pipe is too thin
to support this job. Pushing images took 3 hours so job
Will check it once new nodes arrive.
This reverts commit f2801fabdd.
This time proper approach involves job dependencies.
First we build and publish x86-64 and aarch64 images with architecture
name in image tag. Then we create multiarch manifests to create 'master'
This change modifies the CentOS build CI jobs to use a CentOS 8 host
NOTE: This does not affect the version of CentOS used as the base image
in containers built by kolla.
Partially-Implements: blueprint centos-rhel-8
Partially-Implements: blueprint centos-rhel-python3
If stestr failed, then no node info was logged.
Logging node info is now handled in pre and post stages of Zuul.
Additionally Zuul v3 migration recommendations were applied
and some unused code removed improving general readability.
Signed-off-by: Radosław Piliszek <email@example.com>
When building images for binary type, it is expected to not install
executables from untrusted sources, and gem, sensu-install, npm or
pip packages for instance should come from the distro itself.
This commit adds a `validate-binary-build.sh` script that checks for
forbidden commands in the rendered Dockerfile templates for the binary
type builds and hooks this script with the pep8 CI job.
The output is just informative for now until we've fixed the culprit
Dockerfiles, then we'll make the script return an error code and with
the ability to fail the pep8 CI check. This should prevent unwanted
commands from entering binary type Dockerfiles.
The current code worked only if the project was using the project_name
in kolla/common/config.py, rather than the tarball_base name. This is
only true on master - on stable branches we may switch to use the
tarball_base name, so the regex won't match.
We use the stable branch of the requirements project.
Also add an exception for the crane project, which is not managed by
Make use of 'tarball_base' field to handle tarball renames.
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
Currently CentOS gates use btrfs storage driver and
create /docker device backing btrfs.
This patch is to sync the gate run with Ubuntu.
(post-Trusty) does not use btrfs, only overlay2.
The mkdir instruction tries to create the
/etc/systemd/system/docker.service.d folder wich in some cases might
not exists. This change includes hte -p argument.
Delegate code style validation to computers, they're better than human
at it :)
This commit adds a new `tools/validate-indentation.sh` script that
errors when it finds an indented Dockerfile instruction, and enables
the validation in the pep8 check.
Also adjust the logic of `tools/validate-all-dockerfiles.sh` so that it
doesn't stop on first errors but instead shows all of them.
Fixes the remaining indentations in Dockerfiles.
All release notes must leave in "releasenotes/notes" directory.
One of them has been generated in wrong place
"tools/releasenotes/notes" for Pike release.
This patch just remote it.
Sometimes gates fails due lack of space,
post merge jobs gates fails always for oraclelinux
binary, not being able create a tarball registry.
This change mounts a second disk in opt and moves
registry data to opt.
Disk format commands are excepts from devstack-gate: