<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pipelines and schedulers on </title>
    <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/</link>
    <description>Recent content in Pipelines and schedulers on </description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Fri, 21 Aug 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CAT in Azure DevOps Pipelines</title>
      <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-azure-devops-pipelines/</link>
      <pubDate>Mon, 04 Sep 2023 14:40:56 +0100</pubDate>
      
      <guid>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-azure-devops-pipelines/</guid>
      <description>Prerequisites #A project in Azure Devops A repository containing your CAT project along with test definitions A basic understanding of CAT Before you start #A pipeline is automated use: CAT allows it on the Enterprise plan only, unlocked by a license key stored on the machine that runs the tests — the Starter, Professional and Team plans refuse a run started by a CI/CD platform, and from CAT 3.</description>
    </item>
    
    <item>
      <title>CAT in Azure DevOps Classic Releases</title>
      <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/ados-classic-releases/</link>
      <pubDate>Wed, 08 Nov 2023 10:59:23 +0100</pubDate>
      
      <guid>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/ados-classic-releases/</guid>
      <description>If you use classic releases in Azure DevOps instead of pipelines defined in YAML, the integration of CAT is a bit different than described in our documentation.
This tutorial describes how you can hide sensitive information, such as connection strings or their parts, while still keep and use the same code base locally and in pipelines without any changes. What any pipeline needs besides that — the Enterprise plan, the license key set on the agent (required from CAT 3.</description>
    </item>
    
    <item>
      <title>CAT in GitLab</title>
      <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-gitlab/</link>
      <pubDate>Mon, 04 Sep 2023 14:40:56 +0100</pubDate>
      
      <guid>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-gitlab/</guid>
      <description>Prerequisites #An existing project in GitLab A repository containing CAT project files along with test definitions A basic understanding of CAT Before you start #A pipeline is automated use: CAT allows it on the Enterprise plan only, unlocked by a license key stored on the machine that runs the tests — the Starter, Professional and Team plans refuse a run started by a CI/CD platform, and from CAT 3.</description>
    </item>
    
    <item>
      <title>CAT in GitHub Actions</title>
      <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-github-actions/</link>
      <pubDate>Mon, 04 Sep 2023 14:40:56 +0100</pubDate>
      
      <guid>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-github-actions/</guid>
      <description>Prerequisites #GitHub public or private repository set up CAT project along with test definitions created and pushed to the repository A basic understanding of CAT Before you start #A pipeline is automated use: CAT allows it on the Enterprise plan only, unlocked by a license key stored on the machine that runs the tests — the Starter, Professional and Team plans refuse a run started by a CI/CD platform, and from CAT 3.</description>
    </item>
    
    <item>
      <title>CAT in Jenkins</title>
      <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-jenkins/</link>
      <pubDate>Mon, 04 Sep 2023 14:40:56 +0100</pubDate>
      
      <guid>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-jenkins/</guid>
      <description>Prerequisites #Jenkins installed and set up on your machine. An existing CAT project file along with test definitions A basic understanding of CAT Before you start #A pipeline is automated use: CAT allows it on the Enterprise plan only, unlocked by a license key stored on the machine that runs the tests — the Starter, Professional and Team plans refuse a run started by a CI/CD platform, and from CAT 3.</description>
    </item>
    
    <item>
      <title>CAT in SQL Server Agent</title>
      <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/sql-agent-cat-cli/</link>
      <pubDate>Tue, 21 Nov 2023 06:59:23 +0100</pubDate>
      
      <guid>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/sql-agent-cat-cli/</guid>
      <description>Before you start #SQL Server Agent is a scheduler, and CAT recognizes it as one: an unattended run needs the Enterprise plan and a license key on the machine — from CAT 3.0 a job step without the key stops before any test runs — see Integrations. The key, like the environment variables the project file reads, is per user: set it under the account the job step runs as (the SQL Server Agent service account, or the proxy account of the step), not under your own.</description>
    </item>
    
    <item>
      <title>CAT in Windows Task Scheduler</title>
      <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-windows-task-scheduler/</link>
      <pubDate>Fri, 21 Aug 2026 10:00:00 +0200</pubDate>
      
      <guid>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-windows-task-scheduler/</guid>
      <description>Before you start #A scheduled task is automation, and CAT recognizes Windows Task Scheduler: the run needs the Enterprise plan and a license key — from CAT 3.0 a task without the key stops before any test runs — see Integrations. Decide which Windows account the task runs as — a service account is the usual choice — because three things are stored per user: the license key (%APPDATA%\CAT\.catconfig), user-level environment variables, and the PowerShell module when installed with -Scope CurrentUser.</description>
    </item>
    
    <item>
      <title>CAT in cron</title>
      <link>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-cron/</link>
      <pubDate>Fri, 21 Aug 2026 10:00:00 +0200</pubDate>
      
      <guid>https://docs.justcat.it/how-to-guides/pipelines-and-schedulers/cat-in-cron/</guid>
      <description>Before you start #cron is a scheduler and CAT recognizes it: an unattended run needs the Enterprise plan and a license key — from CAT 3.0 a cron job without the key stops before any test runs — see Integrations. On Linux the tool is the PowerShell module (CAT CLI and the Python module are Windows-only); PowerShell 7 installed per Run CAT on Linux. The providers built on Windows components — Dax@*, PowerBI@*, CsvOleDB@1, ExcelOleDB@1 — are not available here; a cron job tests databases and files.</description>
    </item>
    
  </channel>
</rss>
