Title here
Summary here
Introduction
Description
An Updatecli run prints its result to the console, and the result is lost unless the CI logs are kept. Udash stores it. At the end of a run, Updatecli publishes each pipeline’s report to Udash, and the interface lets you look at every repository at once, filter by label or by result, and follow how a dependency moved over the past weeks.
Warning | Udash is experimental, on both sides. Publishing reports from Updatecli requires the
|
How it works
Udash is a web interface backed by an API and a PostgreSQL database. Updatecli sends its reports to the API over HTTP, from your laptop, from CI, or from a scheduled job. Nothing in your manifests has to change.
Two things in a manifest decide how easily you find a report again:
an
scm, because the interface is organised per Git repositorylabels, because the filters are built on them
See it running
The Updatecli project publishes the reports of its own pipelines to a public instance, updatecli.uda.sh. Anyone can browse it without signing in, which makes it a quick way to see what Udash shows before running your own. Publishing to it is reserved for the Updatecli project.
Getting an instance
To try Udash on your own pipelines, the quick start runs it locally with Docker Compose.
For a shared instance, Udash is published as a Helm chart:
helm repo add updatecli https://updatecli.github.io/charts
helm install udash updatecli/udashDeployment options, authentication, configuration, the in-cluster agent, and the API reference are documented in the updatecli/udash repository.
Go further
Quick start - run it locally in a few minutes.
Sending reports - connect Updatecli to an instance.
Dashboards - what the interface offers once reports arrive.
updatecli/udash - the source, the operator documentation, and the issue tracker.
Next
Github Search