Prow CI/CD Framework
A Prow CI/CD Framework is a CI/CD framework.
- Context:
- It has a Microservice Architecture, such as:
- Prow Hook, which listens to incoming GitHub webhooks,
- Prow Tide, which merges approved PRs,
- Prow Sinker, which cleans up resources that are no longer needed.
- It has a Microservice Architecture, such as:
- See: Skaffold Framework, Draft Framework, Helm Framework, Jenkins Framework.
References
2020
- https://jenkins-x.io/docs/reference/components/prow/
- QUOTE: The CI/CD system that Kubernetes uses to build itself.
Prow is a Kubernetes based CI/CD system. Jobs can be triggered by various types of events and report their status to many different services. In addition to job execution, Prow provides GitHub automation in the form of policy enforcement, chat-ops via /foo style commands, and automatic PR merging.
Prow has a microservice architecture implemented as a collection of container images that run as Kubernetes deployments ...
- QUOTE: The CI/CD system that Kubernetes uses to build itself.
2019
- https://www.inovex.de/blog/spinnaker-vs-argo-cd-vs-tekton-vs-jenkins-x/
- QUOTE: ... Finally, let’s have a look at Jenkins X. CloudBees is the driving force behind this elaborate approach towards a fully-fledged cloud-native CI/CD tool. To make it happen, the creators rely on tools that are already solving parts of the big puzzle that is cloud-native CI/CD. From Skaffold and Draft to Helm and Prow, every tool you probably heard of at the latest KubeCon has its place in Jenkins X. Don’t know what any of those do? Well, according to Jenkins X, you don’t need to. ...
... This tool is so Kubernetes, it doesn’t even have its own repository yet. Prow is located in a subdirectory under github.com/kubernetes/test-infra/, and, spoiler alert, that’s what it does: This is Kubernetes’ very own CI tool, primarily responsible for testing and managing merge requests. As Prow consists of many microservices, the name game is stepped up once more. We have:
- hook, which listens to incoming GitHub webhooks,
- tide, which merges approved PRs,
- sinker, which cleans up resources that are no longer needed.
- All these are running as containers in a Kubernetes cluster. The ProwJob CRD, which represents the life of a webhook trigger in the Prow ecosystem, is essential as well.
- QUOTE: ... Finally, let’s have a look at Jenkins X. CloudBees is the driving force behind this elaborate approach towards a fully-fledged cloud-native CI/CD tool. To make it happen, the creators rely on tools that are already solving parts of the big puzzle that is cloud-native CI/CD. From Skaffold and Draft to Helm and Prow, every tool you probably heard of at the latest KubeCon has its place in Jenkins X. Don’t know what any of those do? Well, according to Jenkins X, you don’t need to. ...