mirror of https://github.com/apache/cassandra
209ef2b6c4
* Add ephemeral-storage requests and limits to agents, and log peak disk usage Agents were evicted at the node level due to lack of disk space. Each pod needs minimum 100GiB, and each template now budgets 80Gi of the ~89Gi that a 100GiB node allocates, with docker's own volume carries a 60Gi sizeLimit. Exceeding either evicts the pod, so logging has been added in each test split before and after the run. All script blocks in Jenkinsfile are now labeled for improved readability in test runs. * `.build/run-ci` must not silently drop a site's helm values customisations Long-lived instances like pre-ci.cassandra.apache.org carry values in addition to the jenkins-deployment.yaml, and any `helm upgrade -f jenkins-deployment.yaml` (or `.build/run-ci`) would drop them. Allow these values to be kept in a separate file, passed in with `--values-override`. Before upgrading helm values, we now compare the deployed values against what is about to be applied and require confirmation for anything only the site holds. This catches added keys and dropped list items (but it cannot catch every change). Also keep the jenkins-home pvc claim on uninstall, so --only-tear-down no longer destroys build history. Add jenkins-test.sh and a gha workflow for test validating changes under .jenkins/ patch by Mick Semb Wever; reviewed by Dmitry Konstantinov for CASSANDRA-21523 |
||
|---|---|---|
| .. | ||
| README.md | ||
| requirements.txt | ||
| run-ci-test.py | ||
| run_ci.py | ||
README.md
Help for .build/run-ci
➤ .build/run-ci --help
usage: run-ci [-h] [-c KUBECONFIG] [-x KUBECONTEXT] [-i URL] [-u USER] [-r REPOSITORY] [-b BRANCH] [-p {packaging,skinny,pre-commit,pre-commit w/ upgrades,post-commit,custom}] [-e PROFILE_CUSTOM_REGEXP] [-j JDK] [-d DTEST_REPOSITORY] [-k DTEST_BRANCH]
[-s] [--only-setup] [-v VALUES_OVERRIDE] [--tear-down] [--only-tear-down] [--only-node-cleaner] [-o DOWNLOAD_RESULTS]
Run CI pipeline for Cassandra on K8s using Jenkins.
options:
-h, --help show this help message and exit
-c KUBECONFIG, --kubeconfig KUBECONFIG
Path to a different kubeconfig.
-x KUBECONTEXT, --kubecontext KUBECONTEXT
Use a different Kubernetes context.
-i URL, --url URL Jenkins url. Suitable when kubectl access in not available. Can also be specified via the JENKINS_URL environment variable (and in .build/.run-ci.env)
-u USER, --user USER Jenkins user. Can also be specified via the JENKINS_USER environment variable (and in .build/.run-ci.env)
-r REPOSITORY, --repository REPOSITORY
Repository URL. Defaults to current tracking remote.
-b BRANCH, --branch BRANCH
Repository branch. Defaults to current branch.
-p {packaging,skinny,pre-commit,pre-commit w/ upgrades,post-commit,custom}, --profile {packaging,skinny,pre-commit,pre-commit w/ upgrades,post-commit,custom}
CI pipeline profile. Defaults to skinny.
-e PROFILE_CUSTOM_REGEXP, --profile-custom-regexp PROFILE_CUSTOM_REGEXP
Regexp for stages when using custom profile. See `testSteps` in Jenkinsfile for list of stages. Example: 'stress.*|jvm-dtest.'
-j JDK, --jdk JDK Specify JDK version. Defaults to all JDKs the current branch supports.
-d DTEST_REPOSITORY, --dtest-repository DTEST_REPOSITORY
DTest repository URL.
-k DTEST_BRANCH, --dtest-branch DTEST_BRANCH
DTest repository branch.
-s, --setup Set up Jenkins before the build.
--only-setup Only install Jenkins into the k8s cluster.
-v VALUES_OVERRIDE, --values-override VALUES_OVERRIDE
Path to an additional helm values file, applied over .jenkins/k8s/jenkins-deployment.yaml. Required when the target cluster carries site customisations, see .jenkins/k8s/README.md
--tear-down Tear down Jenkins after the build.
--only-tear-down Only tear down Jenkins.
--only-node-cleaner Only run the node cleaner. The node cleaner scans the k8s nodes, eagerly terminating those unused.
-o DOWNLOAD_RESULTS, --download-results DOWNLOAD_RESULTS
Just download the results for the specificed build number. Naming of local artefacts assumes current tracking remote and branch, use -r and -b otherwise.
Examples
Run the current directory's fork and branch through the default "pre-commit" pipeline, connecting via your default kubeconfig
.build/run-ci
Do the same but connecting via a jenkins url
.build/run-ci --url pre-ci.cassandra.apache.org --user myuser
Run the the specified fork and branch through the "skinny" pipeline restricted to tests on jdk11
.build/run-ci -r "https://github.com/jrwest/cassandra.git" -b "jwest/15452-5.0" -p "skinny" -j 11
Run the the specified fork and branch through just the "fqltool-test" tests
.build/run-ci -r "https://github.com/jrwest/cassandra.git" -b "jwest/15452-5.0" -p "custom" -e "fqltool-test"
Setup/Update Jenkins Helm into your current kubeconfig
.build/run-ci --only-setup
Setup/Update Jenkins Helm into a cluster that carries site customisations, e.g. pre-ci.cassandra.apache.org
.build/run-ci --only-setup --values-override ~/.cassandra-ci/pre-ci-overrides.yaml
Before any setup, the values already deployed are compared against those about to be applied. Any value the deployed jenkins holds that the new files lack is listed, and confirmation is asked for before it is dropped; running non-interactively aborts instead. See .jenkins/k8s/README.md for what this can and cannot catch.
Uninstall Jenkins from your current kubeconfig.
.build/run-ci --only-tear-down
The jenkins-home volume is kept; delete it separately with kubectl delete pvc cassius-jenkins