The Kata Containers project no longer uses Zuul for CI.
This project is therefore no longer maintained.
Change-Id: I1426be073422ee243d599893ea8e54f12d74d785
As a first step to removing the Kata tenant, stop running jobs
for repositories on GitHub. Those are no longer in the "required"
checks for any repo/branch, and are being replaced by GitHub actions
performing the same check.
Change-Id: I06e7998b5da402549bd6fdcc6a2802814c6dddcb
The web repo (katacontainers.io) is driven by a CMS that cannot be
made to form 'CI compatible' pull requests and commits. As we know
who and where the CMS updates come from, we will just 'trust' that
they conform to the 'chain of trust'. Let's drop the CI checks for
that repo.
Change-Id: I9d59eac10e5d87324734faa5d16f773941eb3077
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
The PR-check was never completely implemented, and does not run
successfully. Remove it's hook from the proxy repo config to stop
spurious Zuul CI failures appearing on PRs.
Change-Id: I080d3656283ffb21307835d8c6b431f38b7fbf15
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
Our CI jobs can take >1h to run, but should take <2h.
Without setting a timeout they hit the default 30m00s
timeout, and fail. Set a timeout at 2h00m (7200s).
Change-Id: I46a8474e0402ddc0550606fe17d8eb460a884405
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
The CI setup scripts may (likely will) install the correct
version of golang into /usr/local/go/* when run. Ensure
we have that in our PATH before the system default go,
else the build will likely fail (due to using the wrong
go version).
The modification is in two places (playbook and role/task),
as afaict there is no mechanism to set an ansible style
`environment` at a higher level, such as the higher level
Zuul jobs.yaml file, that will then persist across all
sub-execution units. We could maybe place the required PATH
into a var, and use that to set the PATH in the lower down
items *if* maintenance becomes too much of a burden.
Change-Id: I34205d5c4397d730eaf266122591140e0647b49b
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
We need to have golang installed as a minimum to run the CI
scripts. Add this as a distro-specific set of files, which
then allows us to:
- specialise in the future per distro if need be
- note (fail gracefully) when we run on a new distro
for the first time.
Note, the distro specific parts are specifically added as a
role as they will not pass the playbook linter if placed
in the playbook tree (they are fragments, and playbooks
are expected to be complete).
Change-Id: Icb675c30a5ddcc5bdbebb7413808a58af4e838b7
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
Add the relevant pipeline, jobs, roles, playbooks etc.
to enable a Kata QA CI build/run on Ubuntu 16.04 triggered
by the relevant github state changes.
Change-Id: Id4174c68856bbb792c002b05e36e36bfe19dbca9
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
A recent fix to wrap YAML long line resulted in an extra \n being
appended to ANSIBLE_ROLES_PATH, resulting in test failure.
Using YAML line folding instead of block folding should solve this.
This change is not self-testing so it may require force-merging.
Change-Id: If59cd536e3111b7c8f75879b0c24de039492cebe
To aid pre-checks before submission, lets make the files pass
the default yamllint checks - then we can use yamllint to check
new changes going forwards.
Changes were:
- change True to true for some bools (which also then matches
the zuul gerrit driver docs)
- add '---' document start lines
- wrap one >80 char line using a '>' string construct
Change-Id: I5c365517606b2c331e7155c56b9ebd7873244b10
Signed-off-by: Graham Whaley <graham.whaley@intel.com>
On https://github.com/kata-containers/tests/pull/1165, for
some reason the URL passed to our WIP-check was from
api.github.com instead of the expected github.com, triggering
a regexp extraction error.
From now on, accept any hostname and just extract repository
and pull request number at the end of the URL.
Change-Id: I79b4d96a84273a97f64b3350e3bd58e8646f0f0f
Closes: https://github.com/kata-containers/ci/issues/111
For each test, point to documentation that explains what
the check is, how to fix it, how to investigate failure,
and how to get more help.
Change-Id: I8a9d6274c0df8233004437cdd5a51d8f13d1cd21
GitHub status checks usually only report in the status check
area -- let's try to optimize for that. We don't have much control
with the current GitHub driver on what shows up there, except
pipeline names and a link.
Separate Gerrit from GitHub pipelines, and rename GitHub pipelines
so that they match the test being run. Avoid comments (at least for
now). Link to the Zuul build results, filtered by the appropriate
pipeline name.
Change-Id: Id9f8848941320b41be86ac62efcf768b33c526db
Create pr-check pipeline that triggers on PR changes (not on
label changes). Add the dco-license job to the kata-prechecks
template.
Change-Id: Iffd6689a2edb95df7d0d4ec6b8e378fc0de20b08
Create a pr-status pipeline that runs on PR changes (including
labeling/unlabeling). Define a kata-pre-checks job template that
runs the kata-github-wip job on that pipeline.
Apply that template to the kata-containers/proxy GitHub repository
for testing.
Depends-On: https://review.openstack.org/634248
Change-Id: I67eb5db8cee02069b1813642f40254420d41075f
Add a kata-github-wip Zuul job that can be used to test
for presence of specific WIP PR labels or specific WIP
keywords in the PR title and block the PR accordingly.
Suppress the placeholder job that was added just to
pass initial tests.
Change-Id: I4f50c77e19f1e76bf65ebfcb9ea587e0556dda03
OpenStack adopted a clean-check requirement for its gate pipeline
(i.e., a change must pass check before being enqueued into gate).
If that is not desired in the kata-containers tenant, this change
will remove it.
Change-Id: Ib24a33031023f7c20d36ae3c21a27bb8d626cf36
This initial commit contains pipeline definitions,
job definitions, and job pipeline definitions for
kata-containers/zuul-config itself.
Includes a minimal placeholder playbook and role so
that the tests actually pass. Those can be removed
once proper playbooks and roles are added.
Depends-On: https://review.openstack.org/630994
Change-Id: I41d4f8a958eaa66e016e0a35e4df68f992ce6009