Difference between revisions of "GitLab Runner"

From wikieduonline
Jump to navigation Jump to search
Line 34: Line 34:
 
# 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>
 
# 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 ==

Revision as of 15:13, 17 November 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 allows to define

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/

New

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
  6. Create a shared runner in Admin area -> Overview -> runners
  7. Setup Autoscaling GitLab Runner on AWS EC2 (GitLab Runner Manager)

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: