| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Current `auth.log` uses `fullpath` and `ip`, while `api_json.log` uses
`remote_ip` and `path` for the same fields. Let's standardize these
namings to make it easier for people working with the data.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66167
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In GitLab 9.0,
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9661 removed the
`subscribed` flag from the API when the user requested a list of issues
or merge requests since calculating this value triggers extensive
Markdown processing.
In GitLab 12.0 via a4fbf39e, we accidentally reintroduced this
performance regression by changing `IssueBasic` to `Issue` in
`entities.rb`. This showed up as a Gitaly N+1 issue since the Markdown
processing would attempt to extract a commit if it detected a regex that
matched a commit.
We restore the prior behavior by once again removing the `subscribed`
flag for the bulk list of issues and merge requests and add a test to
ensure they aren't reintroduced.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/66202
|
|\
| |
| |
| |
| |
| |
| | |
fix handling of empty ref_name parameter string in commits api
Closes #64745
See merge request gitlab-org/gitlab-ce!31687
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
when params[:ref_name] is set to "" by passing an empty query parameter
to the api it is evaluated as false by the || operator.
The use of active support core extensions presence method fixes the original
implemantation.
https://guides.rubyonrails.org/active_support_core_extensions.html#presence
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Eliminate many Gitaly calls in discussions API
Closes #65957
See merge request gitlab-org/gitlab-ce!31834
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, the API to retrieve discussions from merge requests often
generated hundreds of Gitaly calls to determine whether a system note
should be shown to the user. It did this by:
1. Rendering the Markdown
2. Extracting cross-references from the Markdown
3. For cross-references that were commits, a Gitaly FindCommit RPC
would be issued to validate that the commit exists.
The last step is unnecessary because we don't need to display a commit
if the user doesn't have access to the project in the first place.
`RendersNotes#prepare_notes_for_rendering` is already used in
`MergeRequestsController`, which is why we don't see N+1 Gitaly calls
there. We use it here to optimize the note redaction process.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/65957
|
|\ \
| | |
| | |
| | |
| | | |
Adds EE prepend, which for some reason was missing
See merge request gitlab-org/gitlab-ce!31851
|
| |/ |
|
| |
| |
| |
| |
| | |
This was added in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31789
|
| |
| |
| |
| |
| |
| |
| |
| | |
CE-specific changes for:
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/15129
Co-Authored-By: Alex Kalderimis <akalderimis@gitlab.com>
Co-Authored-By: Luke Duncalfe <lduncalfe@eml.cc>
|
|/
|
|
|
| |
This introduces several changes, but these are all just ported from the
EE project.
|
|\
| |
| |
| |
| | |
Resolve EE differences in the lib/ directory
See merge request gitlab-org/gitlab-ce!31582
|
| |
| |
| |
| |
| |
| | |
EE added a single line to this file that can easily be backported to CE,
but it appears this was overlooked. The method called is a noop in CE,
so no additional changes are necessary.
|
|\ \
| | |
| | |
| | |
| | | |
Remove KubernetesService integration
See merge request gitlab-org/gitlab-ce!31365
|
| | |
| | |
| | |
| | |
| | |
| | | |
Creating new records has been disabled, and all
existing records been migrated to clusters as of
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28534
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove label issue and MR counts from default API responses
See merge request gitlab-org/gitlab-ce!31543
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
These counts significantly increase the load time for these
requests. Users can now opt in to receiving the counts by setting
`with_counts=true` in requests. This is a breaking change, but hopefully
a fairly minor one.
|
| | |
| | |
| | |
| | | |
As decided in https://gitlab.com/gitlab-org/gitlab-ce/issues/53593
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
Use NotesFinder#target to find Epics
See merge request gitlab-org/gitlab-ce!31408
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
private profiles here as well
|
| | |
| | |
| | |
| | | |
projects on profile to documentation
|
| | | |
|
| | | |
|
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
API endpoints for requesting container repositories
and container repositories with their tag information
are enabled for users that want to specify the group
containing the repository rather than the specific project.
|
|/
|
|
|
| |
`allow_local_requests_for_hooks_and_services` was renamed to
`allow_local_requests_for_web_hooks_and_services`.
|
|
|
|
|
|
|
|
|
|
| |
Remove project from NotesFinder constructor
Add project parameter to specs
Also look for methods in private scope
Fix specs to match new NotesFinder constructor
|
|
|
|
| |
Creates a new item in help dropdown to show configured support page link
|
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Drop feature to take ownership of a trigger token
Closes #2868
See merge request gitlab/gitlabhq!3198
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Removing API and frontend interactions that allowed
users to take ownership of a trigger token.
Removed mentions from the documentation.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'master'
CE: Add project download & project export audit event
See merge request gitlab-org/gitlab-ce!31103
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
This change adds audit events for
download of repository and export of
project.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Expose git blame in api
Closes #51345
See merge request gitlab-org/gitlab-ce!30675
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Remove code related to object hierarchy and MySQL
Closes #65056 and #65055
See merge request gitlab-org/gitlab-ce!31095
|
| | |/ /
| |/| |
| | | |
| | | |
| | | | |
These are not required because MySQL is not
supported anymore
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Find build by sha from ref
Closes #64534 and #45697
See merge request gitlab-org/gitlab-ce!30843
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
* Reword Project#latest_successful_build_for to
Project#latest_successful_build_for_ref
* Reword Ci::Pipeline#latest_successful_for to
Ci::Pipeline#latest_successful_build_for_ref
|
| |/ / /
|/| | |
| | | |
| | | |
| | | | |
Convert several occurrences of `map` + `flatten` to
`flat_map` where applicable.
|
|/ / /
| | |
| | |
| | | |
None of this code can be reached any more, so it can all be removed
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Multiple pipeline support for Build status
See merge request gitlab-org/gitlab-ce!30828
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds specs for testing the new behavior of specifying a pipeline when
POSTing a status.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This allows user to specify the pipeline ID
when several pipelines has been triggered
on the same branch and commit.
Signed-off-by: Gaetan Semet <gaetan.semet@renault.com>
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
API: Allow changing only ci_default_git_depth
See merge request gitlab-org/gitlab-ce!30888
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
Use correct parent when committing in WebIDE
See merge request gitlab-org/gitlab-ce!29598
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When passing start_branch on committing from the WebIDE, it's possible
that the branch has changed since editing started, which results in the
change being applied on top of the latest commit in the branch and
overwriting the new changes.
By passing the start_sha instead we can make sure that the change is
applied on top of the commit which the user started editing from.
|