| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
see https://gitlab.com/gitlab-org/gitlab-ce/issues/42025
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Remove soft removals related code
Closes #37447
See merge request gitlab-org/gitlab-ce!15789
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes all usage of soft removals except for the "pending delete"
system implemented for projects. This in turn simplifies all the query
plans of the models that used soft removals. Since we don't really use
soft removals for anything useful there's no point in keeping it around.
This _does_ mean that hard removals of issues (which only admins can do
if I'm not mistaken) can influence the "iid" values, but that code is
broken to begin with. More on this (and how to fix it) can be found in
https://gitlab.com/gitlab-org/gitlab-ce/issues/31114.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37447
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Add `pipelines` endpoint to merge requests API
Closes #39214
See merge request gitlab-org/gitlab-ce!15454
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Backport authorized_keys
Closes gitlab-ee#3953
See merge request gitlab-org/gitlab-ce!16014
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add find key by base64 key or fingerprint to the internal API
See merge request !250
Squashed changes:
Add unique index to fingerprint
Add new index to schema
Add internal api to get ssh key by fingerprint
Change API endpoint to authorized_keys
Add InsecureKeyFingerprint that calculates the fingerprint without shelling out
Add require for gitlab key fingerprint
Remove uniqueness of fingerprint index
Remove unique option from migration
Fix spec style in fingerprint test
Fix rubocop complain
Extract insecure key fingerprint to separate file
Change migration to support building index concurrently
Remove those hideous tabs
|
| |/ /
| |
| |
| |
| |
| | |
This will enable admins to identify who actually made the API request.
Relates to #36960
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Expose project_id on /api/v4/pages/domains
See merge request gitlab-org/gitlab-ce!16200
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
[EE-backport] Add group boards API endpoint
See merge request gitlab-org/gitlab-ce!16194
|
| | |/ / |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add online attribute to runner api entity
Closes #25774
See merge request gitlab-org/gitlab-ce!11750
|
| | | | | |
|
| | |/ / |
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
'rd-api-request-to-edit-wiki-page-fails-when-project-belongs-to-group' into 'master'
Fix API endpoints to edit wiki pages where project belongs to a group
Closes #40453
See merge request gitlab-org/gitlab-ce!16170
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In some cases is prefered to manually create a ProjectWiki over using
Project#wiki. This is because Project#wiki always uses the #owner (which
is a User sometimes) as the
author of the wiki changes but sometimes the owner is a Group and it
doesn't respond to #username
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
'ce-4135-remove-ee-specific-code-from-post-api-v4-projects-id-members' into 'master'
Backport part of EE's "Remove EE-specific code from `POST /api/v4/projects/:id/members`"
See merge request gitlab-org/gitlab-ce!16051
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On GitLab.com, there are write deploy keys with no associated users.
Pushes with these deploy keys end with an Error 500 since we attempt
to look up redirect message. If there is no user, don't attempt
to display a redirect message.
Closes #41466
|
| |/ /
| |
| |
| |
| | |
+ Add support for the new separate channel and events settings
* Dry up chat notifications in the service properties definitions
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Resolve "Search merge-requests with API"
Closes #38318
See merge request gitlab-org/gitlab-ce!16029
|
| | | | |
|
| | | |
| | |
| | |
| | | |
- Ensure that unwanted params are no passed to actual finder classes
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, this would include the entire User record in the update
hash, which was rendered in the response using `to_json`, erroneously
exposing every attribute of that record, including their (now removed)
private token.
Now we only include the user ID, and perform the lookup on-demand.
|
| |\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* upstream/master: (671 commits)
Make rubocop happy
Use guard clause
Improve language
Prettify
Use temp branch
Pass info about who started the job and which job triggered it
Docs: add indexes for monitoring and performance monitoring
clearer-documentation-on-inline-diffs
Add docs for commit diff discussion in merge requests
sorting for tags api
Clear BatchLoader after each spec to prevent holding onto records longer than necessary
Include project in BatchLoader key to prevent returning blobs for the wrong project
moved lfs_blob_ids method into ExtractsPath module
Converted JS modules into exported modules
spec fixes
Bump gitlab-shell version to 5.10.3
Clear caches before updating MR diffs
Use new Ruby version 2.4 in GitLab QA images
moved lfs blob fetch from extractspath file
Update GitLab QA dependencies
...
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
Allows ordering in GET api/v4/projects/:project_id/repository/contributors
through `order_by` and `sort` params.
The available `order_by` options are: name|email|commits.
The available `sort` options are: asc|desc.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Prevent creating issues through API without having permissions
See merge request gitlab/gitlabhq!2225
(cherry picked from commit c298bbaa88883343dc9cbbb6abec0808fb3b546c)
915b97c5 Prevent creating issues through API without having permissions
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
[10.2] Ensure we expose group projects using GroupProjectsFinder
See merge request gitlab/gitlabhq!2234
(cherry picked from commit 072f8f2fd6ec794645375a16ca4ddc1cbeb76d7a)
a2240338 Ensure we expose group projects using GroupProjectsFinder
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Moving the check out of the general requests, makes sure we don't have
any slowdown in the regular requests.
To keep the process performing this checks small, the check is still
performed inside a unicorn. But that is called from a process running
on the same server.
Because the checks are now done outside normal request, we can have a
simpler failure strategy:
The check is now performed in the background every
`circuitbreaker_check_interval`. Failures are logged in redis. The
failures are reset when the check succeeds. Per check we will try
`circuitbreaker_access_retries` times within
`circuitbreaker_storage_timeout` seconds.
When the number of failures exceeds
`circuitbreaker_failure_count_threshold`, we will block access to the
storage.
After `failure_reset_time` of no checks, we will clear the stored
failures. This could happen when the process that performs the checks
is not running.
|
| | |
| |
| |
| | |
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/40825
|
| | |\
| | |
| | |
| | |
| | | |
CE backport of "ProtectedBranches API handles per user/group granularity"
See merge request gitlab-org/gitlab-ce!15747
|
| | | |
| | |
| | |
| | |
| | | |
In EE we now allow individual users/groups to be set on POST, which required some refactoring.
See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3516
|
| | | | |
|
| | |\ \
| | |/
| |/|
| | |
| | | |
Multiple artifacts
See merge request gitlab-org/gitlab-ce!14367
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Two things at ones, as there was no clean way to seperate the commit and
give me feedback from the tests.
But the model Artifact is now JobArtifact, and the table does not have a
type anymore, but the metadata is now its own model:
Ci::JobArtifactMetadata.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To allow jobs/builds to have multiple artifacts, and to start seperating
concerns from Ci::Build a new model is created: Ci::Artifact.
Changes include the updating of the ArtifactUploader to adapt to a
slightly different interface. The uploader expects to be initialized
with a `Ci::Build`.
Futher a migration with the minimal fields, the needed foreign keys and
an index.
Last, the way this works is by prepending a module to Ci::Build so we
can basically override behaviour but if needed use `super` to get the
original behaviour.
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Optimize API /groups/:id/projects by preloading assocations
Closes #40308
See merge request gitlab-org/gitlab-ce!15475
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
