Commit 6bd2d594 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Change to new GitLab Runner name

parent 6e6cea23
...@@ -31,12 +31,12 @@ There are three methods to enable the use of `docker build` and `docker run` dur ...@@ -31,12 +31,12 @@ There are three methods to enable the use of `docker build` and `docker run` dur
The simplest approach is to install GitLab Runner in `shell` execution mode. The simplest approach is to install GitLab Runner in `shell` execution mode.
GitLab Runner then executes job scripts as the `gitlab-runner` user. GitLab Runner then executes job scripts as the `gitlab-runner` user.
1. Install [GitLab Runner](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/#installation). 1. Install [GitLab Runner](https://gitlab.com/gitlab-org/gitlab-runner/#installation).
1. During GitLab Runner installation select `shell` as method of executing job scripts or use command: 1. During GitLab Runner installation select `shell` as method of executing job scripts or use command:
```bash ```bash
sudo gitlab-ci-multi-runner register -n \ sudo gitlab-runner register -n \
--url https://gitlab.com/ \ --url https://gitlab.com/ \
--registration-token REGISTRATION_TOKEN \ --registration-token REGISTRATION_TOKEN \
--executor shell \ --executor shell \
...@@ -93,7 +93,7 @@ In order to do that, follow the steps: ...@@ -93,7 +93,7 @@ In order to do that, follow the steps:
mode: mode:
```bash ```bash
sudo gitlab-ci-multi-runner register -n \ sudo gitlab-runner register -n \
--url https://gitlab.com/ \ --url https://gitlab.com/ \
--registration-token REGISTRATION_TOKEN \ --registration-token REGISTRATION_TOKEN \
--executor docker \ --executor docker \
...@@ -178,7 +178,7 @@ In order to do that, follow the steps: ...@@ -178,7 +178,7 @@ In order to do that, follow the steps:
1. Register GitLab Runner from the command line to use `docker` and share `/var/run/docker.sock`: 1. Register GitLab Runner from the command line to use `docker` and share `/var/run/docker.sock`:
```bash ```bash
sudo gitlab-ci-multi-runner register -n \ sudo gitlab-runner register -n \
--url https://gitlab.com/ \ --url https://gitlab.com/ \
--registration-token REGISTRATION_TOKEN \ --registration-token REGISTRATION_TOKEN \
--executor docker \ --executor docker \
......
...@@ -501,8 +501,8 @@ First start with creating a file named `build_script`: ...@@ -501,8 +501,8 @@ First start with creating a file named `build_script`:
```bash ```bash
cat <<EOF > build_script cat <<EOF > build_script
git clone https://gitlab.com/gitlab-org/gitlab-ci-multi-runner.git /builds/gitlab-org/gitlab-ci-multi-runner git clone https://gitlab.com/gitlab-org/gitlab-runner.git /builds/gitlab-org/gitlab-runner
cd /builds/gitlab-org/gitlab-ci-multi-runner cd /builds/gitlab-org/gitlab-runner
make make
EOF EOF
``` ```
......
...@@ -267,10 +267,10 @@ terminal execute: ...@@ -267,10 +267,10 @@ terminal execute:
```bash ```bash
# Check using docker executor # Check using docker executor
gitlab-ci-multi-runner exec docker test:app gitlab-runner exec docker test:app
# Check using shell executor # Check using shell executor
gitlab-ci-multi-runner exec shell test:app gitlab-runner exec shell test:app
``` ```
## Example project ## Example project
......
...@@ -57,7 +57,7 @@ First install [Docker Engine](https://docs.docker.com/installation/). ...@@ -57,7 +57,7 @@ First install [Docker Engine](https://docs.docker.com/installation/).
To build this project you also need to have [GitLab Runner](https://about.gitlab.com/gitlab-ci/#gitlab-runner). To build this project you also need to have [GitLab Runner](https://about.gitlab.com/gitlab-ci/#gitlab-runner).
You can use public runners available on `gitlab.com`, but you can register your own: You can use public runners available on `gitlab.com`, but you can register your own:
``` ```
gitlab-ci-multi-runner register \ gitlab-runner register \
--non-interactive \ --non-interactive \
--url "https://gitlab.com/" \ --url "https://gitlab.com/" \
--registration-token "PROJECT_REGISTRATION_TOKEN" \ --registration-token "PROJECT_REGISTRATION_TOKEN" \
......
...@@ -52,7 +52,7 @@ First install [Docker Engine](https://docs.docker.com/installation/). ...@@ -52,7 +52,7 @@ First install [Docker Engine](https://docs.docker.com/installation/).
To build this project you also need to have [GitLab Runner](https://about.gitlab.com/gitlab-ci/#gitlab-runner). To build this project you also need to have [GitLab Runner](https://about.gitlab.com/gitlab-ci/#gitlab-runner).
You can use public runners available on `gitlab.com`, but you can register your own: You can use public runners available on `gitlab.com`, but you can register your own:
``` ```
gitlab-ci-multi-runner register \ gitlab-runner register \
--non-interactive \ --non-interactive \
--url "https://gitlab.com/" \ --url "https://gitlab.com/" \
--registration-token "PROJECT_REGISTRATION_TOKEN" \ --registration-token "PROJECT_REGISTRATION_TOKEN" \
......
...@@ -61,7 +61,7 @@ correctly with your CI jobs: ...@@ -61,7 +61,7 @@ correctly with your CI jobs:
1. First, make sure you have used [relative URLs](#configuring-the-gitmodules-file) 1. First, make sure you have used [relative URLs](#configuring-the-gitmodules-file)
for the submodules located in the same GitLab server. for the submodules located in the same GitLab server.
1. Next, if you are using `gitlab-ci-multi-runner` v1.10+, you can set the 1. Next, if you are using `gitlab-runner` v1.10+, you can set the
`GIT_SUBMODULE_STRATEGY` variable to either `normal` or `recursive` to tell `GIT_SUBMODULE_STRATEGY` variable to either `normal` or `recursive` to tell
the runner to fetch your submodules before the job: the runner to fetch your submodules before the job:
```yaml ```yaml
...@@ -71,7 +71,7 @@ correctly with your CI jobs: ...@@ -71,7 +71,7 @@ correctly with your CI jobs:
See the [`.gitlab-ci.yml` reference](yaml/README.md#git-submodule-strategy) See the [`.gitlab-ci.yml` reference](yaml/README.md#git-submodule-strategy)
for more details about `GIT_SUBMODULE_STRATEGY`. for more details about `GIT_SUBMODULE_STRATEGY`.
1. If you are using an older version of `gitlab-ci-multi-runner`, then use 1. If you are using an older version of `gitlab-runner`, then use
`git submodule sync/update` in `before_script`: `git submodule sync/update` in `before_script`:
```yaml ```yaml
......
...@@ -126,7 +126,7 @@ always in-sync with the codebase. ...@@ -126,7 +126,7 @@ always in-sync with the codebase.
[GitLab Workhorse]: https://gitlab.com/gitlab-org/gitlab-workhorse [GitLab Workhorse]: https://gitlab.com/gitlab-org/gitlab-workhorse
[Gitaly]: https://gitlab.com/gitlab-org/gitaly [Gitaly]: https://gitlab.com/gitlab-org/gitaly
[GitLab Pages]: https://gitlab.com/gitlab-org/gitlab-pages [GitLab Pages]: https://gitlab.com/gitlab-org/gitlab-pages
[GitLab Runner]: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner [GitLab Runner]: https://gitlab.com/gitlab-org/gitlab-runner
[GitLab Omnibus]: https://gitlab.com/gitlab-org/omnibus-gitlab [GitLab Omnibus]: https://gitlab.com/gitlab-org/omnibus-gitlab
[GitLab QA]: https://gitlab.com/gitlab-org/gitlab-qa [GitLab QA]: https://gitlab.com/gitlab-org/gitlab-qa
[part of GitLab Rails]: https://gitlab.com/gitlab-org/gitlab-ce/tree/master/qa [part of GitLab Rails]: https://gitlab.com/gitlab-org/gitlab-ce/tree/master/qa
......
...@@ -184,7 +184,7 @@ Runner. ...@@ -184,7 +184,7 @@ Runner.
We recommend using a separate machine for each GitLab Runner, if you plan to We recommend using a separate machine for each GitLab Runner, if you plan to
use the CI features. use the CI features.
[security reasons]: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/security/index.md [security reasons]: https://gitlab.com/gitlab-org/gitlab-runner/blob/master/docs/security/index.md
## Supported web browsers ## Supported web browsers
......
...@@ -456,7 +456,7 @@ A route table contains rules (called routes) that determine where network traffi ...@@ -456,7 +456,7 @@ A route table contains rules (called routes) that determine where network traffi
### Runners ### Runners
Actual build machines/containers that [run and execute tests](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner) you have specified to be run on GitLab CI. Actual build machines/containers that [run and execute tests](https://gitlab.com/gitlab-org/gitlab-runner) you have specified to be run on GitLab CI.
### Sidekiq ### Sidekiq
......
...@@ -49,8 +49,8 @@ git log --since=1.month.ago --until=3.weeks.ago ...@@ -49,8 +49,8 @@ git log --since=1.month.ago --until=3.weeks.ago
``` ```
cd ~/workspace cd ~/workspace
git clone git@gitlab.com:gitlab-org/gitlab-ci-multi-runner.git git clone git@gitlab.com:gitlab-org/gitlab-runner.git
cd gitlab-ci-multi-runner cd gitlab-runner
git log --author="Travis" git log --author="Travis"
git log --since=1.month.ago --until=3.weeks.ago git log --since=1.month.ago --until=3.weeks.ago
git log --since=1.month.ago --until=1.day.ago --author="Travis" git log --since=1.month.ago --until=1.day.ago --author="Travis"
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment