diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-09-05 15:08:33 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-09-05 15:08:33 +0300 |
commit | ef1719209ecbc60ec714d283455e47ac040b7a79 (patch) | |
tree | 26f38e5c8f8f0aa377a81cd45467d7e7e1b6dad1 | |
parent | 58b9df24e628a143fee76e966f962c7b7209f4b2 (diff) |
Add latest changes from gitlab-org/gitlab@master
-rw-r--r-- | doc/development/cicd/index.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/cicd/index.md b/doc/development/cicd/index.md index 38f7c391313..28cf67105f6 100644 --- a/doc/development/cicd/index.md +++ b/doc/development/cicd/index.md @@ -100,7 +100,7 @@ A job with the `created` state won't be seen by the Runner yet. To make it possi When the Runner is connected, it requests the next `pending` job to run by polling the server continuously. NOTE: **Note:** -API endpoints used by the Runner to interact with GitLab are defined in [`lib/api/runner.rb`](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/api/runner.rb) +API endpoints used by the Runner to interact with GitLab are defined in [`lib/api/ci/runner.rb`](https://gitlab.com/gitlab-org/gitlab/blob/master/lib/api/ci/runner.rb) After the server receives the request it selects a `pending` job based on the [`Ci::RegisterJobService` algorithm](#ciregisterjobservice), then assigns and sends the job to the Runner. |