We'll configure docker hub auto build to automatically rebuild the
system container for the origin CI when we push changes to a given
branch (master for this PR). Docker Hub will rebuild from master and
tag docker.io/crio/cri-o:v3.9 to be used in the Origin CI.
The same will be done for the following branches->tags:
release-1.7 -> docker.io/crio/cri-o:v3.7
release-1.8 -> docker.io/crio/cri-o:v3.8
master -> docker.io/crio/cri-o:v3.9
The only moving bit will be the master branch, we need to re-configure
docker hub auto builds whenever we branch out from master for the next
CRI-O release.
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
Signed-off-by: Wei Wei <weiwei.inf@gmail.com>
Make pid namespace sharing optional and disabled by default
We reverse the logic so that pid ns sharing is disabled by default.
Signed-off-by: Mrunal Patel <mrunalp@gmail.com>
This allows us to cache a k8s branch for cri-o 1.0 branch
while allowing overriding of k8s branch in master and other
newer cri-o branches.
Signed-off-by: Mrunal Patel <mrunalp@gmail.com>
Update vendor/github.com/vbatts/tar-split to v0.10.2, to fix
CVE-2017-14992, per https://github.com/vbatts/tar-split/pull/42.
Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
Depending on the state of upstream repositories, it's possible the
kubernetes repo could change between the ``setup`` and ``run`` phase.
Alternatively, something during ``setup`` itself could mangle the repo.
Add an option to force clone the kubernetes repo. This gives support
for testing on multiple CRI-O branches, realizing some benefit from
caching, yet also allows hauling in brand-new-kubernetes for the e2e
tests.
Signed-off-by: Chris Evich <cevich@redhat.com>
kpod removal actually removed all man1 docs but the Makefile was still
referencing man1 stuff. CRI-O doesn't have man1 so let's drop that
altogether now.
Signed-off-by: Antonio Murdaca <runcom@redhat.com>
* Skip some tests if the bridge-custom plugin is
unavailable. This CNI plugin is not distributed in
any RPM, it is only available by compiling from a
side branch in runcom's private github. We can't
use it in a real integration-test setting.
* Don't use `run()` inside cleanup handlers. It will
override $status, which is a double whammy:
- successful cleanup will mask a test failure
- when a test is `skip()`ed, crictl may fail,
and $status will indicate failure.
* seccomp test: use existing $SECCOMP_PROFILE instead of
assuming a path under $CRIO_ROOT
Signed-off-by: Ed Santiago <santiago@redhat.com>
