Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://gitlab.com/gitlab-org/gitlab-runner

GitLab Runner is the open source project that is used to run your CI/CD jobs and send the results back to GitLab
https://gitlab.com/gitlab-org/gitlab-runner

hacktoberfest

Last synced: 5 days ago
JSON representation

GitLab Runner is the open source project that is used to run your CI/CD jobs and send the results back to GitLab

Host: gitlab.com
URL: https://gitlab.com/gitlab-org/gitlab-runner
Owner: gitlab-org
License: mit
Created: 2015-04-27T21:10:25.322Z (over 9 years ago)
Default Branch: main
Last Synced: 2024-04-14T10:15:34.881Z (8 months ago)
Topics: hacktoberfest
Stars: 2,318
Forks: 2,178
Open Issues: 8,888
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Codeowners: .gitlab/CODEOWNERS
- Security: docs/security/index.md

Awesome Lists containing this project

awesome-robotic-tooling - gitlab-runner - Runs tests and sends the results to GitLab. (Development Environment / Build and Deploy)
awesome-robotic-tooling - gitlab-runner - runs tests and sends the results to GitLab (Development Environment / Build and Deploy)
awesome-docker - GitLab Runner - GitLab has integrated CI to test, build and deploy your code with the use of GitLab runners. (Development with Docker / CI/CD)
awesome-docker - GitLab Runner - GitLab has integrated CI to test, build and deploy your code with the use of GitLab runners. (Development with Docker / CI/CD)

README

# GitLab Runner

This is the repository of the official GitLab Runner written in Go.
It runs tests and sends the results to GitLab.
[GitLab CI](https://about.gitlab.com/gitlab-ci) is the open-source
continuous integration service included with GitLab that coordinates the testing.
The old name of this project was GitLab CI Multi Runner but please use "GitLab Runner" (without CI) from now on.

[![Pipeline Status](https://gitlab.com/gitlab-org/gitlab-runner/badges/main/pipeline.svg)](https://gitlab.com/gitlab-org/gitlab-runner/commits/main)
[![Go Report Card](https://goreportcard.com/badge/gitlab.com/gitlab-org/gitlab-runner)](https://goreportcard.com/report/gitlab.com/gitlab-org/gitlab-runner)

## Runner and GitLab CE/EE compatibility

For a list of compatible versions between GitLab and GitLab Runner, consult
the [compatibility section](https://docs.gitlab.com/runner/#gitlab-runner-versions).

## Release process

The description of release process of GitLab Runner project can be found inside of [`PROCESS.md`](PROCESS.md).

## Contributing

Contributions are welcome, see [`CONTRIBUTING.md`](CONTRIBUTING.md) for more details.

### Closing issues

GitLab is growing very fast and we have limited resources to deal with
issues opened by community volunteers. We appreciate all the
contributions coming from our community, but we need to create some
closing policy to help all of us with issue management.

The issue tracker is not used for support or configuration questions. We
have dedicated [channels](https://about.gitlab.com/support/) for these
kinds of questions. The issue tracker should only be used for feature
requests, bug reports, and other tasks that need to be done for the
Runner project.

It is up to a project maintainer to decide if an issue is actually a
support/configuration question. Before closing the issue the maintainer
should leave a reason why this is a support/configuration question, to make
it clear to the issue author. They should also leave a comment using
[our template](https://gitlab.com/gitlab-org/gitlab-runner/blob/main/PROCESS.md#support-requests-and-configuration-questions)
before closing the issue. The issue author has every right to disagree and
reopen the issue for further discussion.

### Contributing to documentation

If your contribution contains only documentation changes, you can speed up the CI process
by following some branch naming conventions, as described in

## Documentation

The documentation source files can be found under the [docs/](docs/) directory. You can
read the documentation online at .

## Features

[Read about the features of GitLab Runner.](https://docs.gitlab.com/runner/#features)

## Executors compatibility chart

[Read about what options each executor can offer.](https://docs.gitlab.com/runner/executors/#compatibility-chart)

## Install GitLab Runner

Visit the [installation documentation](https://docs.gitlab.com/runner/install/).

## Use GitLab Runner

See [https://docs.gitlab.com/runner/commands/](https://docs.gitlab.com/runner/commands/).

## Select executor

See [https://docs.gitlab.com/runner/executors/#selecting-the-executor](https://docs.gitlab.com/runner/executors/#selecting-the-executor).

## Troubleshooting

Read the [FAQ](https://docs.gitlab.com/runner/faq/).

## Advanced Configuration

See [https://docs.gitlab.com/runner/configuration/advanced-configuration.html](https://docs.gitlab.com/runner/configuration/advanced-configuration.html).

## Building and development

See [https://docs.gitlab.com/runner/development/](https://docs.gitlab.com/runner/development/).

## Changelog

Visit the [Changelog](CHANGELOG.md) to view recent changes.

## The future

- Please see the [GitLab Direction page](https://about.gitlab.com/direction/).
- Feel free submit issues with feature proposals on the issue tracker.

## Author

- 2014 - 2015 : [Kamil Trzciński](mailto:[email protected])
- 2015 - now : GitLab Inc. team and contributors

## License

This code is distributed under the MIT license, see the [LICENSE](LICENSE) file.