Difference between revisions of "GitLab Runner"

From wikieduonline
Jump to navigation Jump to search
Line 21: Line 21:
 
* <code>[[gitlab-runner status]]</code>
 
* <code>[[gitlab-runner status]]</code>
 
* <code>[[gitlab-runner list]]</code> (Provides executor information Executor=docker|Executor=shell)
 
* <code>[[gitlab-runner list]]</code> (Provides executor information Executor=docker|Executor=shell)
 +
* <code>[[gitlab-runner exec docker validate]]</code>
 
* <code>[[gitlab-runner exec]] docker --docker-privileged $JOB</code>
 
* <code>[[gitlab-runner exec]] docker --docker-privileged $JOB</code>
  

Revision as of 05:44, 12 August 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 allows to define

  • how many jobs you can run in parallel concurrent option
  • Integration with sentry
  • Integration with Prometheus

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/

Activities

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

Related terms

See also

  • 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
  • Advertising: