- 22 Mar, 2017 2 commits
-
-
dimitrieh authored
-
Annabel Dunstone Gray authored
-
- 20 Mar, 2017 38 commits
-
-
Annabel Dunstone Gray authored
-
Alfredo Sumaran authored
Append _spec to group_name_toggle spec file Closes #29491 See merge request !9975
-
Achilleas Pipinellis authored
Simplify trigger_docs build job for CE and EE See merge request !9820
-
Annabel Dunstone Gray authored
Fix input token spacing See merge request !10090
-
Alfredo Sumaran authored
Removed d3.js from the main application.js bundle Closes #29608 See merge request !10062
-
Jose Ivan Vargas Lopez authored
-
Annabel Dunstone Gray authored
Fixed filter bar alignment issues Closes #29543 See merge request !10049
-
Sean McGivern authored
Merge branch '20204-new-issue-button-redirects-you-to-create-a-new-issue-after-logging-in' into 'master' Redirect to signin when New Issue for not logged in Closes #20204 See merge request !9743
-
Achilleas Pipinellis authored
Merge branch '29713-update-documentation-to-reflect-prometheus-monitors-k8s-by-default' into 'master' Update docs to indicate prometheus k8s monitoring is on by default See merge request !10089
-
Clement Ho authored
-
Rémy Coutable authored
Update deploy keys documentation See merge request !10084
-
Sean McGivern authored
Add closed_at field to issues Closes #27212 See merge request !9977
-
Joshua Lambert authored
-
Joshua Lambert authored
-
Joshua Lambert authored
-
Yorick Peterse authored
Remove repeated routes.path check for postgresql database See merge request !10063
-
Sam Rose authored
-
Rémy Coutable authored
Fix Project Wiki update Closes #29405 See merge request !9990
-
Dongqing Hu authored
-
Adam Niedzielski authored
-
Rémy Coutable authored
Use google-protobuf 3.2.0.2 See merge request !10014
-
Rémy Coutable authored
Update 8.12-to-8.13.md: gitlab version 8.13 wants gitlab-shell v3.6.7 See merge request !10071
-
Sean McGivern authored
Todos performance: Include associations in Finder See merge request !10076
-
Kamil Trzciński authored
Fix regressions introduced while adding CI endpoints in API v4 See merge request !9952
-
Rémy Coutable authored
Allow dot in branch name in trigger/builds endpoint in API Closes #29438 See merge request !10001
-
George Andrinopoulos authored
-
winniehell authored
-
winniehell authored
-
Jarka Kadlecova authored
-
Sean McGivern authored
Allow creating merge request even if target branch is not specified in query params Closes #28890 See merge request !9968
-
Sean McGivern authored
Allow unauthenticated access to some Branch API GET endpoints Closes #29662 See merge request !10077
-
Jacob Vosmaer authored
-
Tomasz Maczukin authored
-
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.
-