---
title: "Pipelines and schedulers"
description: "Running CAT unattended — CI/CD platforms and schedulers, step by step"
url: "https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/"
---
# Pipelines and schedulers


Running CAT unattended, step by step per platform. Whatever runs it — Azure DevOps, GitLab, GitHub Actions, Jenkins, SQL Server Agent, Windows Task Scheduler, cron — needs the same four things, and the [Integrations](https://docs.justcat.it/reference/integrations/ "Integrations reference") page has them on one screen: the **Enterprise plan** (unattended use is refused on the others), the **license key** set on the machine under the account that runs CAT (from CAT 3.0 an unattended run without it stops before any test), the **secrets as environment variables** that account can see, and a way to turn results into a verdict — a report file the platform renders, or a step that reads the summary, because CAT itself exits `0` when the run completed.