GitLab runner

Gitlab Runner released in January 2015 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

• Runners cache: [runners.cache] https://docs.gitlab.com/runner/configuration/advanced-configuration.html#the-runnerscache-section

Commands

• gitlab-runner verify
• gitlab-runner list

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

• git: [config | init | status ], git add, git rm, git commit, git push, git pull, .gitconfig, .gitignore, git (clone, fetch, pull), git tag, git log, git blame, Merge Request, LFS, git branch, git apply, git rebase, git diff, git diff-tree, git config --global, remote | submodule | request-pull, GIT_TRACE, GIT_CURL_VERBOSE, clean, main, git show-ref, git reset, git prune, git ls-remote origin, git checkout, git switch, pathspec, git credential-osxkeychain, git version, pre-commit, git --help, GitBook, refs/
• gitlab-ci.yml (CI/CD pipelines)

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