Difference between revisions of "GitLab runner"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 21: | Line 21: | ||
== See also == | == See also == | ||
| − | * {{ | + | * {{gitlab-ci.yml}} |
* {{gitlab runner}} | * {{gitlab runner}} | ||
Latest revision as of 13:41, 30 August 2022
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: /etc/gitlab-runner/config.toml. Read https://docs.gitlab.com/runner/configuration/advanced-configuration.html
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
Commands[edit]
gitlab-runner verifygitlab-runner list
Activities[edit]
- 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
See also[edit]
gitlab-ci.yml,job: | stage: | stages: | artifacts: | include: | script: | when: | only: | needs:- Gitlab runner, runners:
gitlab-runner,gitlab-ci.yml,config.toml, GitLab Runner Changelog
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy.
Source: wikiversity
Advertising:
