Install machine runner 3.0 on Windows
On This Page
This page describes how to install CircleCI’s machine runner 3.0 on Windows. This has been tested for Windows Server 2016, 2019, and 2022 in Datacenter Edition. Other Server SKUs with Desktop Experience and Remote Desktop Services (RDS) should also work.
This page walks you through installing a machine runner and its dependencies (for example, Chocolatey, Git, and Gzip) on your Windows Server.
Since this setup creates a new local administrator user that runs CircleCI jobs, your Windows Server needs to be capable of creating local users and accepting remote logons for them.
The Windows Server needs to be a domain member when you set this up in domain environments. The self-hosted runner instance cannot run on a Windows Server operating as a domain controller. |
Prerequisites
To install machine runners and run jobs, you will need to have root access, and have the following dependencies installed on your system:
-
The CircleCI CLI if you wish to install runners from the command line
Additional utilities and tools, such as Chocolatey, Git, and Gzip are automatically installed as part of the installation script. |
Self-hosted runner terms agreement
Before you can install self-hosted runners through the web app, you will need to agree to the CircleCI Runner Terms. To be able to gain access to the Self-Hosted Runners section of the CircleCI web app or your CircleCI server app, an admin in your organization needs to navigate to , and agree to the terms.
Once the terms have been accepted, Self-Hosted Runners will appear permanently in the side navigation.
Your role within your org is determined differently depending on how you integrate with your code, as follows:
-
If your code is integrated with CircleCI via the GitHub OAuth App or Bitbucket Cloud, CircleCI mirrors VCS permissions for organizations. If you are an admin on your organization’s VCS, you are an admin on CircleCI. If you are unsure, check the admin permissions on your VCS.
-
If your code is integrated with CircleCI via the GitHub App, GitLab, or Bitbucket Data Center, you can check roles by navigating to Roles and permissions overview.
. Full details on roles and permissions are available in the
To find out which GitHub integration you are using, head to the CircleCI web app, select your org, select Organization Home from the sidebar, and inspect the URL in your browser:
For more information about the differences, see the GitHub docs comparison page. |
1. Create namespace and resource class
In order to install self-hosted runners, you will need to create a namespace and resource class token. To create resource classes and tokens, you need to be an organization admin in the VCS provider. You can read about namespaces and resource classes on the Concepts page.
You can view your installed runners on the inventory page, by clicking Self-Hosted Runners on the left navigation.
-
On the CircleCI web app, navigate to Self-Hosted Runners and select Create Resource Class.
-
Next, you will create a custom resource class to use when configuring jobs to use your self-hosted runners. If this is your organization’s first time using self-hosted runners. You will need to create or enter a namespace. If your organization already creates orbs, do not create a new namespace, but instead enter the namespace your organization uses for orbs here too. Enter aname for your self-hosted runner resource class.
Each organization can only create a single namespace. While not required, we suggest using a lowercase representation of your CircleCI account name. CircleCI will populate your org name as the suggested namespace by default in the UI. -
Copy and save the resource class token. Self-hosted runners use this token to claim work for the associated resource class.
The token cannot be retrieved again, be sure to store it safely. -
Select the Machine tab and progress on to the platform-specific instructions in the next section of this installation guide.
2. Machine runner installation on Windows
-
Download the
Install-CircleCIRunner.ps1
script from GitHub to an easily accessible location. -
Open PowerShell as an administrator and navigate to the directory where you placed the script file.
-
Run the following in your PowerShell:
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; ./Install-CircleCIRunner.ps1
The installation will be output into your PowerShell interface.
-
As part of the installation, the configuration file for the machine runner (
runner-agent-config.yaml
) will open in Notepad. Fill in the requested information (see Machine Runner 3.0 Configuration Reference). The configuration file is located in the installation directory,C:\Program Files\CircleCI
, by default.
After your setup completes, the machine runner starts automatically and begins looking for jobs to process.
Machine runner configuration example
Once you have installed configuration runner, select Continue in the CircleCI web app and you will be presented with an example configuration snippet showing a job configured to use your new self-hosted runner resource class.
The fields you must set for a specific job to run using your machine runners are:
-
machine: true
-
resource_class: <namespace>/<resource-class>
Simple example of how you could set up a job:
version: 2.1
workflows:
build-workflow:
jobs:
- runner
jobs:
runner:
machine: true
resource_class: <namespace>/<resource-class>
steps:
- run: echo "Hi I'm on Runners!"
The job will then execute using your self-hosted runner when you push the .circleci/config.yml
to your VCS provider.
Uninstall / reinstall steps
Uninstalling machine runners will prepare the system for installation again.
-
Download the
Uninstall-CircleCIRunner.ps1
script from GitHub to an easily accessible location. -
Open PowerShell as an administrator and navigate to the directory where you placed the script file.
-
Run the following in your PowerShell:
./Uninstall-CircleCIRunner.ps1
Continuous mode vs. single task mode for Windows self-hosted runners
By default, Windows machine runners run in single-task mode in order to ensure high reliability of the underlying technology that the self-hosted runner uses to execute jobs. This is the recommended mode for Windows machine runners.
A Windows machine runner can be run in continuous
mode. However, doing so eliminates the guarantee of a clean job environment. This may translate into jobs not executing as expected, and job failure.
Troubleshooting
Refer to the Troubleshoot Machine Runner guide if you encounter issues installing or running machine runner on Windows.