GitLab Runner
GitLab Runner is the continuous integration and continuous delivery (CI/CD) executor for GitLab. It is responsible for running automated build and test jobs. Its extensibility is relatively limited.
Timeline (last 90 days)
Improper executor configuration of GitLab Runner may allow jobs to escape to the host machine; it is recommended to ensure that the Runner runs in non-privileged mode.
GitLab Runner is the agent process that actually executes CI/CD jobs; jobs defined in a Pipeline are ultimately picked up and executed by some Runner.
GitLab uses a tag matching mechanism: a job declares the required tags in its configuration, and only Runners carrying those tags can pick up that job.
When the Shell executor runs a job, the Runner directly invokes commands on the host (such as Maven), and the job shares the host's file system; the Docker executor, by contrast, runs each job in an isolated container, providing better isolation.
Bases such as GitLab Runner have limited extension capabilities and are not suitable for directly taking on the role of an AI testing team platform.
All Facts (5)
Improper executor configuration of GitLab Runner may allow jobs to escape to the host machine; it is recommended to ensure that the Runner runs in non-privileged mode.
50%UnverifiedGitLab Runner is the agent process that actually executes CI/CD jobs; jobs defined in a Pipeline are ultimately picked up and executed by some Runner.
50%UnverifiedGitLab uses a tag matching mechanism: a job declares the required tags in its configuration, and only Runners carrying those tags can pick up that job.
50%UnverifiedWhen the Shell executor runs a job, the Runner directly invokes commands on the host (such as Maven), and the job shares the host's file system; the Docker executor, by contrast, runs each job in an isolated container, providing better isolation.
50%UnverifiedBases such as GitLab Runner have limited extension capabilities and are not suitable for directly taking on the role of an AI testing team platform.
50%