Vetrix Docs

CI/CD

The CI/CD pages cover the work a repository does on its own: the pipelines it runs from a vetrix-ci.yml file, the jobs and logs those runs produce, the coverage and security results they report, and the environments and deployments they ship to. They are written for anyone who pushes code to a repository with CI/CD enabled; some controls, such as starting a run or editing pipeline variables, appear only when you have permission to run CI/CD on that repository.

Where to find it: open a repository and select Pipelines in the left sidebar, at gitvetrix.com/<owner>/<repo>/pipelines. The Pipelines page gathering recent runs across your repositories is at gitvetrix.com/pipelines. The Security, Environments, and Deployments views are reached from the same repository.

The pages below are ordered as a newcomer meets them, from setting a pipeline up to shipping what it built.

Set up and run pipelines

  • Configuring a pipeline — add the vetrix-ci.yml file that defines your pipeline, read the trigger label on each run, and add, rotate, and delete the write-only pipeline variables stored per branch.
  • Pipelines — read a repository's pipeline runs and the cross-repository CI/CD overview, filter the list, start, cancel, retry, or delete a run, follow a run's jobs and logs and download its artifacts, and set the repository's CI/CD policy and attached hosts.

Read what a run reported

  • Code coverage — read the Coverage report panel on a pipeline's detail page, with the percentage of statements covered for that run, its covered, total, and package counts, and the link to the full HTML report when the run saved one.
  • Security findings — trigger a vulnerability or secret scan, read a completed scan's findings, browse the deduplicated Findings list with its filters and exports, dismiss findings with a recorded reason, and review detected secret alerts.

Ship to an environment

  • Environments — browse a repository's deployment targets as cards showing tier and health, open one to read its current deployment and protection rules, roll back to an earlier deployment, and adjust a blue-green traffic split.
  • Deployments — read the repository's deployment history across every environment, filter it by environment and state, and open the environment a deployment targets.