- 28 Aug, 2017 1 commit
-
-
Robert Schilling authored
-
- 09 Aug, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 02 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 05 Jul, 2017 1 commit
-
-
Nick Thomas authored
-
- 21 Jun, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 14 Jun, 2017 1 commit
-
-
Robert Speicher authored
-
- 12 Jun, 2017 2 commits
-
-
Kamil Trzcinski authored
-
Tomasz Maczukin authored
-
- 21 Apr, 2017 1 commit
-
-
Jacopo authored
Removed all the unnecessary include of `WaitForAjax` and `ApiHelpers` in the specs. Removed unnecessary usage of `api:true`
-
- 06 Apr, 2017 1 commit
-
-
Kamil Trzciński authored
-
- 05 Apr, 2017 1 commit
-
-
Mike Wyatt authored
-
- 20 Mar, 2017 5 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
In APIv1 we've been sending all jobs from previous stages and a `dependencies` list with names of jobs that user want to download artifacts from. This was selected on Runners side. In APIv1 we've planned to send only jobs that were defined (if any; and all previous jobs by default). However I've missed the fact that it was Runner who selected jobs, not GitLab. And now current version of APIV4 sends all jobs everytime. This commit fixes this. If user will define `dependencies` in his job, then GitLab will send only selected jobs.
-
Tomasz Maczukin authored
Artifacts download for authorization is using a job token of job to which the artifact belongs. In APIv1 the token was sent with dependent jobs details and in APIv4 it was designed to also contain it. However I forgot about this parameter while working on `/api/v4/jobs/request` endpoint. This commit adds a missing parameter which is required for APIv4 to work properly.
-
Tomasz Maczukin authored
In Runner v1.3.0 we've started to send User-Agent header with Runner's version data. Since GitLab v8.12.0 we've started to use this header to check if used Runner's version supports 204 status code instead of 404 as a response when there is no jobs to execute by a Runner. In APIv4 (introduced in GitLab 9.0.0) will require Runner v9.0.0. And writing more accurately: GitLab Runner v9.0.0 will require GitLab at least 9.0.0. Because of such breaking change we are able to switch entirely to 204 response code and there is no need to do check of User-Agent. This commit removes useless code and complexity.
-
Tomasz Maczukin authored
In APIv1 we were using UpdateJob to verify if the runner exists. It was the only method that was using Runner's token and used in special way had no side effects (like scheduling a new job or unregisterring a Runner). In APIv4 we've change UpdateJob to use job's token as authentication credentials, and that way we've removed the only endpoint that could be used to verify if the Runner with a certain token exists in target GitLab installation. This commit adds `POST /api/v4/runners/verify` endpoint whose only responsibility is to respond if Runner with posted credentials exists or not.
-
- 16 Mar, 2017 1 commit
-
-
Z.J. van de Weg authored
-
- 13 Mar, 2017 1 commit
-
-
Tomasz Maczukin authored
-
- 07 Mar, 2017 1 commit
-
-
Tomasz Maczukin authored
-
- 06 Mar, 2017 2 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
- 02 Mar, 2017 11 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
- 28 Feb, 2017 1 commit
-
-
Robert Schilling authored
-
- 16 Feb, 2017 3 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-