Skip to content
Branch: master
Clone or download
Latest commit bac33e2 May 23, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Added `bosh deployment` and `bosh environment` info to issue template Jun 11, 2018
concourse Add scripts for deploying vsphere bosh director and concourse workers Mar 21, 2019
configurations
docker-images
etcd
gaffer Update gaffer pools Feb 5, 2019
manifests
scripts
specs Use busybox for dns tests May 22, 2019
src Use busybox for dns tests May 22, 2019
tasks Add task to check whether kubo release and kubo-deployment version ma… May 7, 2019
templates Add task to check whether kubo release and kubo-deployment version ma… May 7, 2019
terraform Load balance GCP with TCP LBs May 28, 2018
vsphere-nginx
.envrc
.gitignore
README.md
bump-bosh-releases.yml Use bosh.io releases in bump pipeline Jan 16, 2019
bump-etcd.yml
bump-flannel.yml
bump-golang.yml
bump-k8s.yml Break bump-k8s into 3 tasks. May 16, 2019
bump-stemcell.yml Upload stemcell using resource for precompiling Dec 6, 2018
cleanup-gcp.yml Use cloudfoundry-incubator for kubo-ci in all pipelines Oct 30, 2018
gaffer.yml Use Bosh deployment in gaffer environment Nov 27, 2018
housekeeper.sh
kubo-deployment-pr.yml Destroy bosh requires git-bosh-deployment resource Nov 28, 2018
kubo-deployment.yml Remove no longer used ship-it part of the pipeline Feb 6, 2019
kubo-release-pr.yml
kubo-windows.yml
long-lived-openstack.yml Stop using ops-file to remove bosh-dns addon in pipelines Nov 23, 2018
openstack.md
recycle.yml Add aws to recycle pipeline Feb 5, 2019
set_pipeline Lpass is no longer used in set_pipeline Nov 29, 2017
ship-it.yml Bump minor when cutting the release Feb 8, 2019
signals-aggregator.yml Add security pipeline to signal aggregator (#59) Apr 30, 2019
update_pipelines
v2_set_pipeline Modify upload-stemcell to upload windows stemcell Mar 21, 2019
vsphere-cleaner.yml Use new interpolation for pipeline configs Jul 3, 2017

README.md

Continuous Integration (CI) for Cloud Foundry Container Runtime (CFCR)

Coverage

Repos covered by the pipelines:

Other related repos:

  • Kubo disaster recovery acceptance tests (kdrats) - Provides tests used by pipelines contained within this repo.
  • [Kubo locks] - provides configuration information for the CI environments used by the pipelines. Private repo for CFCR team use.

Pipelines

To view the pipelines visit ci.kubo.sh

Testing

Kubo-deployment

The main pipeline, runs on every commit in kubo-release and kubo-deployment. Is also used to create Github releases. Runs tests on GCP, AWS and vSphere.

Long-lived-openstack

Runs tests on Openstack with a long-lived director instead of a freshly-deployed one for each run. Configuring OpenStack and Creating New Environments

custom-CIDRs

Tests the CIDRS suite of the integration tests. It tests changing the Pod and Service CIDRs for kubernetes.

Istio

Tests whether Istio specifications can be deployed on CFCR, and the Istio integration tests are run.

Gaffer

Attempts to update the CFCR deployment on which the gaffer application is run. The gaffer application backs https://gaffer.kubo.sh

kubo-release-pr & kubo-deployment-pr

Test pull requests to the repos. Have to be triggered manually.

pod-security-policy

Tests that the PodSecurityPolicy admission controller and policies work as expected.

CFCR-etcd

Tests the etcd release used in CFCR with different configurations. Creates and destroys the cluster at each run.

CFCR-etcd-long-running

Uses a long-lived etcd cluster and specifically focuses on potential “split brain” failure scenarios, centred around network partitions and VM restarts.

Bumping components

The bump-* pipelines are used to automatically update components of CFCR or the CI infrastructure. The docker-boshrelease pipeline tests and releases new versions of the docker release.

Building docker images

This pipeline builds all the images used in the other pipelines based on the dockerfiles located in kubo-ci.

Maintaining CI IaaS environments

The recycle pipeline is used to clean up environments. It is triggered automatically whenever a lock is released by the pipeline using that environment. The cleanup-gcp is used to clean up leftover LoadBalancers and Disks in GCP. The vsphere-cleaner pipeline generates a binary which is used by the recycle pipeline to clean vsphere environments.

You can’t perform that action at this time.