![]() The Custom executor allows you to specify your own executionĮnvironments. ![]() This executor, but usually we recommend using one of the other types. ![]() We have some success stories from organizations using It makes GitLab Runner connect to an external serverĪnd runs the builds there. The SSH executor is added for completeness, but it’s the least supportedĪmong all executors. The executor will call the Kubernetes cluster APIĪnd create a new Pod (with a build container and services containers) for 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |