aa062513c0
On occasion the scripts that use the GitHub API fail without logging any
useful error:
./scripts/get_github_labels.py --id=1568 --has-label=ci/skip/e2e
Traceback (most recent call last):
File "./scripts/get_github_labels.py", line 71, in <module>
main()
File "./scripts/get_github_labels.py", line 55, in main
names = get_names(json)
File "./scripts/get_github_labels.py", line 40, in get_names
names.append(label['name'])
TypeError: string indices must be integers
While debugging, it seems that the limit of API calls is reached:
403 Client Error: rate limit exceeded
It is useful to have failure messages reported in the output of the CI
jobs for future potential troubleshooting.
Signed-off-by: Niels de Vos <ndevos@redhat.com>
Continuous Integration Jobs for the CentOS CI
- dedicated Jenkins instance for Ceph-CSI
- Jenkins is hosted on OpenShift in the CentOS CI
- scripts and Jenkins jobs are hosted in the Ceph-CSI repository (ci/centos branch)
- a Jenkins Pipeline is used to reserve bare metal system(s), and run jobs on those systems
Repository/Branch Structure
This is the ci/centos branch, where all the scripts for the Jenkins jobs are
maintained. The tests that are executed by the jobs are part of the normal
projects branches.
As an example, the containerized-tests Jenkins job consists out of the
following files:
-
jobs/containerized-tests.yamlis a Jenkins Job Builder configuration that describes the events when the job should get run and fetches the.groovyfile from the git repository/branch -
containerized-tests.groovyis the Jenkins Pipeline that contains the stages for the Jenkins Job itself. In order to work with the bare-metal machines from the CentOS CI, it executes the following stages:- dynamically allocate a Jenkins Slave (
node('cico-workspace')) with tools and configuration to request a bare-metal machine - checkout the
centos/cibranch of the repository, which contains scripts for provisioning and preparing the environment for running tests - reserve a bare-metal machine with
cico(configured on the Jenkins Slave) - provision the reserved bare-metal machine with additional tools and
dependencies to run the test (see
prepare.shbelow) - run
make containerized-testsandmake containerized-buildin parallel - as final step, return the bare-metal machine to the CentOS CI for other users (it will be re-installed with a minimal CentOS environment again)
- dynamically allocate a Jenkins Slave (
-
prepare.shinstalls dependencies for the test, and checks out the git repository and branch (or Pull Request) that contains the commits to be tested (and the test itself)
Deploying the Jenkins Jobs
The Jenkins Jobs are described in Jenkins Job Builder configuration files and
Jenkins Pipelines. These need to be imported in the Jenkins instance before
they can be run. Importing is done with the jenkins-jobs command, which runs
in a jjb container. To build the container, and provide the configuration for
Jenkins Job Builder, see the documentation in the deploy/
directory.