| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Closes #29631
|
| |\
| |
| |
| |
| | |
Fix regressions introduced while adding CI endpoints in API v4
See merge request !9952
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| |/
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Ensure dots in project and group ID are allowed in the API endpoints
Closes #27988
See merge request !9944
|
| | |
| |
| |
| |
| |
| | |
API routes
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |/
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
Create a new issue for a single discussion
See merge request !8266
|
| | | |
|
| | |
| |
| |
| |
| | |
merge_request_for_resolving_discussions ->
merge_request_to_resolve_discussions_of
|
| | | |
|
| | |
| |
| |
| |
| | |
And deduplicate the finding of MR's & discussions. Now the searching
is done in the service, istead of the controller & the API.
|
| | |
| |
| |
| |
| |
| | |
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.
|
| | | |
|
| |/
|
|
| |
to make sure we mean the global permissions
|
| | |
|
| |\
| |
| |
| |
| | |
# Conflicts:
# doc/api/v3_to_v4.md
|
| | |
| |
| |
| | |
v3 and several improvements
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
GET "projects/:id/repository/commits" endpoint improvements
Closes #1381 and #20207
See merge request !9679
|
| | | | |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`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
|
| | |
| |
| |
| | |
It was actually not used anywhere.
|
| | |
| |
| |
| |
| | |
Since issues also accepts the query parameter iids[]=, also make it
possible query scope like that.
|
| |/
|
|
| |
Add endpoint to get the jobs scoped to a pipeline.
|
| | |
|
| |\
| |
| |
| |
| | |
Update storage settings to allow extra values per shard
See merge request !9597
|
| | |
| |
| |
| |
| |
| |
| | |
This will be necessary when adding gitaly settings. This version
doesn't make any functional changes, but allows us to include this
breaking change in 9.0 and add the needed extra settings in the future
with backwards compatibility
|
| |\ \
| | |
| | |
| | | |
'origin/personal_access_token_api_and_impersonation_token'
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
to generate non impersionation tokens
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Feature/runner jobs v4 api
Closes #28513
See merge request !9273
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
