Set up Prow on your own GitHub organization to automate test runs and merge management for pull requests.
Use Testgrid to build a visual history dashboard of test results across your CI jobs over time.
Add or change job configurations for Kubernetes CI by submitting an ordinary pull request to this repository.
Use the label syncing tool to keep issue labels consistent across multiple related GitHub repositories.
| kubernetes/test-infra | kubernetes/enhancements | egonelbre/gophers | |
|---|---|---|---|
| Stars | 4,002 | 3,878 | 3,799 |
| Language | Go | Go | Go |
| Setup difficulty | hard | easy | easy |
| Complexity | 4/5 | 1/5 | 1/5 |
| Audience | ops devops | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires a running Kubernetes cluster, cloud project resources, and a GitHub App with appropriate permissions to operate Prow.
kubernetes/test-infra is the home of the tools and configuration that keep the Kubernetes project's testing and automation running. Kubernetes is a large open-source project with thousands of contributors, and this repository contains the plumbing that makes sure every code change gets tested reliably before it is merged. The central piece is a system called Prow, which acts as the project's CI (continuous integration) coordinator. When someone opens or updates a pull request on any Kubernetes repository, Prow is responsible for kicking off the right tests, showing results, and eventually helping merge the code once everything passes. Job configurations for what to test and how are all stored in this repository and updated through ordinary pull requests, so anyone can propose changes to the test setup. The repository also includes several dashboards and supporting tools. Testgrid shows a visual history of test results over time. Triage groups together similar test failures across all jobs so patterns are easier to spot. Deck and the Tide pages show what jobs are running and which pull requests are queued for merging. Beyond Prow, the repo contains smaller utilities: tools to manage pools of cloud project resources used by tests, a proxy to avoid hitting GitHub API rate limits, label synchronization tools across repositories, and scripts that feed test result data into analytics. The whole system is written primarily in Go.
The tools and configuration that run all automated testing and CI for the Kubernetes project, centered on Prow, a system that triggers tests on pull requests, shows results, and manages code merging.
Mainly Go. The stack also includes Go, Kubernetes, Docker.
No license information was explicitly stated in the explanation.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.