FIPS compliant GitLab RunnerĪs of GitLab Runner 14.7, we provide a FIPS 140-12 compliant GitLab Runner binary. Developers expected to work in parallel.įor more information, see what machine types are available for Linux (x86-64) on SaaS.GitLab Runner instances can be sized individually given these variables and scaled higher or lower as necessary. GitLab Runner system requirements vary widely and depend on a number of variables unique to each use-case. GitLab Runner runs the CI/CD jobs that are defined in GitLab.

This instance can be self-managed, or you can use. Settings > CI / CD, expanding the Runners section, and clickingĪfter you install GitLab Runner, you must register individual runners with your GitLab instance. You can also view installation instructions in GitLab by going to your project’s

You can find information on the different installation methods below. If you prefer to use aĭifferent operating system that is not officially supported, it must be able to compile aįor security and performance reasons, you should install GitLab Runner on a machine that is separate to the machine that hosts your GitLab instance. GitLab Runner officially supports the following operating systems. CentOS, Debian, Ubuntu, RHEL, Fedora, Mint, Oracle, Amazon.Official packages are available for the following Linux distributions: GitLab Runner officially supported binaries are available for the following architectures: By using a repository for rpm/deb packages.GitLab Runner can be installed and used on GNU/Linux, macOS, FreeBSD, and Windows. GitLab Runner can also run inside a Docker container or be deployed to a Kubernetes cluster. It can runĪs a single binary and has no language-specific requirements. GitLab Runner is open-source and written in Go. You can install GitLab Runner on your infrastructure. FIPS compliant GitLab Runner in other systems and architectures.

For ios instal Optimizer 15.4