You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 12, 2018. It is now read-only.
@@ -184,23 +197,15 @@ In order to update the runner to a new version just go to runner directory and d
184
197
sudo su gitlab_ci_runner
185
198
cd~/gitlab-ci-runner
186
199
git fetch
187
-
git checkout VERSION_YOU_NEED # Ex. v4.0.0
200
+
git checkout VERSION_YOU_NEED # Ex. v5.0.0
188
201
bundle
189
202
```
190
203
191
204
And restart runner
192
205
193
206
## Easily add Runners to existing GitLab CI
194
207
195
-
GitLab.com uses GitLab CI to test our own builds. To quickly spin up some extra runners in time of need, we have setup a runner as described above, with all the relevant dependencies for our builds and have taken a snapshot of this runner.
196
-
197
-
To quickly add a runner, have the registration token at hand and:
198
-
199
-
- instantiate a new VPS with the snapshot `gitlab-ci-runner-2gb-2gbswap`
200
-
-`bundle exec ./bin/setup`
201
-
-`sudo service gitlab-ci-runner start`
202
-
203
-
Now the runner will start to pick up builds automatically. When you are done with it, you can destroy the VPS without worrying about anything. For testing GitLab itself, use of a runner with >= 2GB RAM is recommended.
208
+
See [omnibus gitlab runner](https://gitlab.com/gitlab-org/omnibus-gitlab-runner/blob/master/doc/install/README.md).
0 commit comments