It can beĬompletely isolated or shared between each build.
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 kommentar(er)
