Difference between revisions of "GitLab Runner"
Jump to navigation
Jump to search
↑ https://docs.gitlab.com/runner/
↑ https://gitlab.com/gitlab-org/gitlab-runner/commit/6f1b10ef6d72de4afc0937ca9337b41be543d64c
↑ https://gitlab.com/gitlab-org/gitlab-runner/issues/3856#note_127887227
(→New) |
|||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 33: | Line 33: | ||
# Read [[GitLab release notes]] | # Read [[GitLab release notes]] | ||
# Learn differences between [[TeamCity|TeamCity Agents]] and [[DevOps/GitLab/GitLab Runner|Gitlab runners]] | # Learn differences between [[TeamCity|TeamCity Agents]] and [[DevOps/GitLab/GitLab Runner|Gitlab runners]] | ||
| + | # Create a [[shared runner]] in <code>[[Admin area]] -> Overview -> runners</code> | ||
| + | # Setup Autoscaling GitLab Runner on AWS EC2 ([[GitLab Runner Manager]]) | ||
== Related terms == | == Related terms == | ||
* [[TeamCity agents]] | * [[TeamCity agents]] | ||
* <code>[[gitlab-runner --help]]</code> | * <code>[[gitlab-runner --help]]</code> | ||
| − | * [[Runners]] | + | * [[CI/CD Runners]] |
| + | * [[GitLab executors]] | ||
| + | * [[There has been a runner system failure, please try again]] | ||
| + | * [[GitHub runner]] | ||
== See also == | == See also == | ||
* {{gitlab-runner}} | * {{gitlab-runner}} | ||
* {{gitlab runner}} | * {{gitlab runner}} | ||
| − | * {{GitLab}} | + | * {{GitLab CI}} |
| − | |||
| − | |||
| − | |||
[[Category:Gitlab]] | [[Category:Gitlab]] | ||
Latest revision as of 07:42, 9 February 2023
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[edit]
/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[edit]
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[edit]
- Credential Helpers GitLab Runner 12.0 https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#use-credential-helpers
Activities[edit]
- 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
- Create a shared runner in
Admin area -> Overview -> runners - Setup Autoscaling GitLab Runner on AWS EC2 (GitLab Runner Manager)
Related terms[edit]
- TeamCity agents
gitlab-runner --help- CI/CD Runners
- GitLab executors
- There has been a runner system failure, please try again
- GitHub runner
See also[edit]
- 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:
