GitLab Runner
GitLab Runner[1] released in January 2015[2] and written in Go offers continuous integration in GitLab, it is used to run your CI/CD jobs and send the results back to GitLab.
Configuration allows to define
- How many jobs you can run in parallel
concurrentoption - Integration with sentry
- Integration with Prometheus
- Runners cache: [runners.cache] https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscache-section
Configuration
/etc/gitlab-runner/config.toml. Read https://docs.gitlab.com/runner/configuration/advanced-configuration.html
Known problems: shell executor doesn't clean up build directories [3]
Commands
Full command list: https://docs.gitlab.com/runner/commands/
gitlab-runner --helpgitlab-runner verifygitlab-runner statusgitlab-runner list(Provides executor information Executor=docker|Executor=shell)gitlab-runner exec docker validategitlab-runner exec docker --docker-privileged $JOB
New
Activities
- Install Gitlab runner
- Read GitLab Runner Changelog, approximately monthly releases: https://gitlab.com/gitlab-org/gitlab-runner/blob/master/CHANGELOG.md
- Read GitLab CI/CD Pipeline Configuration Reference:
.gitlab-ci.ymlhttps://docs.gitlab.com/ee/ci/yaml/ - Read GitLab release notes
- Learn differences between TeamCity Agents and Gitlab runners
Related terms
See also
- Gitlab Runner:
gitlab-runner[status | verify | list]gitlab-runner --help,GIT_STRATEGY - Gitlab runner, runners:
gitlab-runner,gitlab-ci.yml,config.toml, GitLab Runner Changelog - GitLab CI, variables, templates, executors,
.gitlab-ci.yml, .gitlab/, Credential helpers, notifications, pipeline editor, Keyword reference, Changelog,ContainersNotReady, GitLab environments
Advertising:
