# Ci Build Windows

Ci Build Windows is a Docker build container that gives developers a consistent, isolated environment for compiling, testing, and automating Windows software builds in continuous integration (CI) pipelines. It is open source and self-hosted, installable on Docker Hub.

Canonical page: https://ourlocalhost.com/app/6049/ci-build-windows

## Description

Ci Build Windows is a Docker build container that gives developers a consistent, isolated environment for compiling, testing, and automating Windows software builds in continuous integration (CI) pipelines.

## Platform availability

Available on 0 of 10 platforms.

## Health score

51/100 (Fair), based on 2 of 4 factors.
- Easy to install: 25 (0 install platforms, install notes, Docker image)
- Light to run: 85 (500 MB minimum RAM)

## Links

- Docker Hub: https://hub.docker.com/r/grafana/ci-build-windows

## Common questions

### What code-hosting service does a self-hoster mention for a self-hosted CI stack?

A user planning a self-hosted stack says Gitea is needed for code hosting.

### Can a Windows build setup be converted from Buildkite to GitHub Actions?

Contributors discuss moving from Buildkite to GitHub Actions, using custom runners, and converting Windows builds.

### What deployment gotcha can appear on a self-hosted Windows Server 2019 machine?

A PowerShell step can start the application momentarily and then shut it down, even though the script works when typed directly in PowerShell.

### Can a self-hosted GitHub Actions job stay queued when the runner is online?

Yes, a user reports randomly queued jobs while the runner is online and active, after a workflow had run normally for more than a year.

---
Source: Our Local Host (https://ourlocalhost.com/app/6049/ci-build-windows), the self-hosted and open-source app directory.
