The Kubernetes executor allows you to use an existing Kubernetes clusterįor your builds. It works like the normal Docker executorīut with build hosts created on demand by Docker Machine. The Docker Machine is a special version of the Docker executor The Docker executor allows you to easily createĪ build environment with dependent services, With easy dependency management (all dependencies for building the project canīe put in the Docker image). Its usage can also be useful for reducingĪ great option is to use Docker as it allows a clean build environment, Virtual machine and runs the build on it. Machines on Windows, Linux, macOS or FreeBSD, then GitLab Runner connects to the Your builds on different operating systems, since it allows the creation of virtual This type of executor allows you to use an already created virtual machine, which Virtual Machine executor (VirtualBox / Parallels) Your builds need to be installed manually on the same machine that GitLab Runner is Shell is the simplest executor to configure. To break out of their container and access the file system hosting the runner. However, security flaws or certain configurations could allow jobs ![]() ![]() System including the runner’s token, and the cache and code of other jobs.Įxecutors marked ✓ don’t allow the runner to access the file system by default. When a runner’s file system access is not protected, jobs can access the entire.It can beĬompletely isolated or shared between each build. Dependent on what kind of environment you are provisioning.It requires to install all dependencies by hand.It’s possible, but in most cases it is problematic if the build uses services.Executor SSH Shell VirtualBox Parallels Docker Kubernetes Custom Clean build environment for every build ✗ ✗ ✓ ✓ ✓ ✓ conditional (4) Reuse previous clone if it exists ✓ ✓ ✗ ✗ ✓ ✗ conditional (4) Runner file system access protected (5) ✓ ✗ ✓ ✓ ✓ ✓ conditional Migrate runner machine ✗ ✗ partial partial ✓ ✓ ✓ Zero-configuration support for concurrent builds ✗ ✗ (1) ✓ ✓ ✓ ✓ conditional (4) Complicated build environments ✗ ✗ (2) ✓ (3) ✓ (3) ✓ ✓ ✓ Debugging build problems easy easy hard hard medium medium medium The table below shows the key facts for each executor which will help The executors support different platforms and methodologies for building a You can initialize Git LFS on an entire system with git lfs install -system. Ensure Git LFS is up to date on any systems where GitLab Runner uses these executors.īe sure to initialize Git LFS for the user that executes GitLab Runner commands with git lfs install. GitLab Runner uses the git lfs command if Git LFS is installed Always use the latest available version of Git. Installation on the target machine and in the PATH. Prerequisites for non-Docker executorsĮxecutors that do not rely on a helper image require a Git To jump into the specific documentation for each executor, visit: ![]() Out what features each executor does and does not support. If you are not sure what to select, read the GitLab Runner implements a number of executors that can be used to run yourīuilds in different scenarios. Virtual Machine executor (VirtualBox / Parallels).
0 Comments
Leave a Reply. |