Difference between revisions of "GitLab Runner"

From wikieduonline
Jump to navigation Jump to search
Line 6: Line 6:
 
* how many jobs you can run in parallel <code>concurrent</code> option
 
* how many jobs you can run in parallel <code>concurrent</code> option
 
* Integration with [[sentry]]
 
* Integration with [[sentry]]
* Integration with [[Prometheus monitoring|Prometheus]]
+
* Integration with [[Prometheus]]
  
 
*  Runners cache: [runners.cache] https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscache-section
 
*  Runners cache: [runners.cache] https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscache-section

Revision as of 15:40, 12 January 2020

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 concurrent option
  • Integration with sentry
  • Integration with Prometheus

Commands

Activities

  1. /Read GitLab Runner Changelog/, approximately monthly releases: https://gitlab.com/gitlab-org/gitlab-runner/blob/master/CHANGELOG.md
  2. Read GitLab CI/CD Pipeline Configuration Reference:.gitlab-ci.yml https://docs.gitlab.com/ee/ci/yaml/
  3. Read GitLab release notes
  4. Learn differences between TeamCity Agents and Gitlab runners

See also

  • https://docs.gitlab.com/runner/
  • https://gitlab.com/gitlab-org/gitlab-runner/commit/6f1b10ef6d72de4afc0937ca9337b41be543d64c
  • Advertising: