The test-infra repository contains a collection of tools for testing Kubernetes and displaying Kubernetes tests results. There is no merge bot here. Feel free to click the big green merge button once your code is reviewed and passes on Travis. You will need to be a member of kubernetes/test-infra-maintainers to merge.

We use Bazel to build and test the code in this repo. The commands bazel build //... and bazel test //... should be all you need for most cases. If you modify Go code, run ./verify/update-bazel.sh to keep BUILD files up-to-date.

The YAML files under jenkins/job-configs define our Jenkins jobs via Jenkins Job Builder. Travis will run jenkins/diff-job-config-patch.sh to print out the XML diff between your change and master.

The detail of how to create new jobs can be found here.

• The Kubernetes TestGrid shows the results of test jobs for the last few weeks. It is currently not open-sourced, but we we would like to move in that direction eventually.
• The 24-hour test history dashboard collects test results from the last 24 hours. It is updated hourly by the scripts under jenkins/test-history.
• Gubernator is a Google App Engine site that parses and presents the results from individual test jobs.
• Prow is the system that handles GitHub events and commands for Kubernetes. It also has separate dashboards show results for postsubmit jobs and periodic jobs.
• Triage Dashboard shows occurance of each failing test entry among all the running jobs.

The Kubernetes project encourages organizations to contribute execution of e2e test jobs for a variety of platforms (e.g., Azure, rktnetes). The test-history scripts gather e2e results from these federated jobs. For information about how to contribute test results, see Federated Testing.