- 20 Mar, 2017 7 commits
-
-
Adam Niedzielski authored
Closes #29631
-
George Andrinopoulos 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.
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 17 Mar, 2017 2 commits
-
-
Kamil Trzciński authored
-
Oswaldo Ferreira authored
-
- 16 Mar, 2017 2 commits
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Jacopo authored
Added the ability to 'Undo mark all as done' todos marked as complete with 'Mark all as done' in the 'Todo' tab of the Todo dashboard. The operation undos only the todo previously marked as done with the 'Mark al as done' button.
-
- 14 Mar, 2017 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 13 Mar, 2017 5 commits
-
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
merge_request_for_resolving_discussions -> merge_request_to_resolve_discussions_of
-
Bob Van Landuyt authored
-
Bob Van Landuyt authored
And deduplicate the finding of MR's & discussions. Now the searching is done in the service, istead of the controller & the API.
-
Bob Van Landuyt authored
Delegate a discussion in a merge request into a new issue. The discussion wil be marked as resolved and a system note will be added linking to the newly created issue.
-
- 09 Mar, 2017 3 commits
-
-
http://jneen.net/ authored
-
http://jneen.net/ authored
to make sure we mean the global permissions
-
George Andrinopoulos authored
-
- 08 Mar, 2017 5 commits
-
-
Oswaldo Ferreira authored
-
George Andrinopoulos authored
-
Jordan Ryan Reuter authored
`Kaminari.paginate_array` takes some options, most relevant of which is a `total_count` parameter. Using the `commit_count` for `total_count` lets us correctly treat the return of `Repository#commits` as a subset of all the commits we may wish to list. Addition of a new `Repository#commit_count_for_ref` method was necessarry to allow the user to start from an arbitrary ref. Ref #1381
-
Felipe Artur authored
Remove unecessary endpoint from repository, add compatibility endpoints for v3 and several improvements
-
Felipe Artur authored
-
- 07 Mar, 2017 12 commits
-
-
Toon Claes authored
It was actually not used anywhere.
-
Toon Claes authored
Since issues also accepts the query parameter iids[]=, also make it possible query scope like that.
-
Toon Claes authored
Add endpoint to get the jobs scoped to a pipeline.
-
Kamil Trzciński authored
-
Tomasz Maczukin authored
-
Timothy Andrew authored
- Typo in docs - Newline between test/expectation in `api/issues_spec` - Use `find_by` instead of `reference_by` in the structure defining awardables
-
Timothy Andrew authored
- Use issue/merge_request IID instead of ID - Duplicate the original `TimeTrackingEndpoints` concern (+ specs) for V3, since this is a breaking change.
-
Timothy Andrew authored
- Instead of `issuable_id`
-
Timothy Andrew authored
- Instead of `merge_request_id` and `issue_id` - The API also deals with `snippet_id`, which remains unchanged (since snippets don't have `iid`s - Duplicate the original `AwardEmoji` API (and spec) for use with the V3 API, since this is a breaking change.
-
Timothy Andrew authored
- Instead of `merge_request_id` - Duplicate the original `MergeRequestDiffs` API (and spec) for use with the V3 API, since this is a breaking change.
-
Timothy Andrew authored
- As opposed to the `id` that was previously being used. - This brings the API routes closer to the web interface's routes. - This is specific to API v4.
-
Timothy Andrew authored
- As opposed to the issue `id` that was previously being used. - This brings the API routes closer to the web interface's routes. - This is specific to API v4.
-
- 06 Mar, 2017 3 commits
-
-
Tiago Botelho authored
-
Robert Speicher authored
-
Oswaldo Ferreira authored
-