Feature
Pipelines and Pipeline runs
Record the CI/CD definition of each Application and every execution of it, with Commit statuses beside them.
A Pipeline is the CI/CD definition that builds and ships an Application. A Pipeline run is one execution of it, with a status from NOT_STARTED to SUCCEEDED, FAILED or CANCELED.
Commit statuses are status checks on a repository commit, keyed by owner, repo, sha and context. Reading them needs no token. Writing one needs org:contributor and write access to the matching Application, or the ci:agent Machine role, so CI can report with a Service account PAT.
Pipelines can be copied to another Application, and each record keeps its own Mode.
More features
All features →- 01
Application lifecycle
Create, configure and delete Applications with Quotas per Cluster, Namespaces, Ownership links and Extended resources.
- 02
Deployment tracking
Follow each Deployment of an Application on a Cluster, with service type, DNS, Stages and Events.
- 03
Clusters and Quotas
List and inspect the Kubernetes Clusters Deployments run on, and hold each Application’s CPU, memory and jobs allowance per Cluster.