Age | Commit message (Collapse) | Author |
|
In order to save user preferences regarding
user emails allowed to be invited to group
Add foreign_key and down method
Change adding foreign key
Add partial call to view
Add changelog entry
Fix schema
|
|
To index notes, we exclude system notes and use `find_in_batches` to
load them in batches for submission to the ES bulk import API.
These queries often result in DB timeouts because the usage of
`ORDER BY id` results in the `notes_pkey` index being used.
This adds an optimized partial index, and removes the unused index
`index_notes_on_noteable_type` which is already covered for our
usage by the existing `index_notes_on_noteable_id_and_noteable_type`.
Newer versions of PostgreSQL (at least 11) are smarter about this and
use `index_notes_on_project_id_and_noteable_type` instead, so we might
be able to remove the partial index again in the future.
|
|
This change lays the foundation for customizable cycle analytics stages.
The main reason for the change is to extract the event definitions to
separate objects (start_event, end_event) so that it could be easily
customized later on.
|
|
- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level
|
|
|
|
|
|
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14943
See merge request gitlab-org/gitlab-ce!31406
|
|
'13208-epicissue-has-an-unexpected-default-relative-position-ce' into 'master'
[CE] Remove default `relative_position` from `epic_issues`
See merge request gitlab-org/gitlab-ce!31514
|
|
'4221-board-milestone-should-persist-any-none-properly-ce' into 'master'"
This reverts merge request !30613
|
|
Remove KubernetesService integration
See merge request gitlab-org/gitlab-ce!31365
|
|
This makes `epic_issues` consistent with other tables
using our `RelativePositioning` class
|
|
|
|
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
|
|
- This will make it easy to identify the project even if admins change
the name of the project or move it.
|
|
Docker Registry Replication
|
|
|
|
Kubernetes deployments on new clusters will now have
a separate namespace per project environment, instead
of sharing a single namespace for the project.
Behaviour of existing clusters is unchanged.
All new functionality is controlled by the
:kubernetes_namespace_per_environment feature flag,
which is safe to enable/disable at any time.
|
|
Improve the performance of viewing deploy keys
Closes #43080
See merge request gitlab-org/gitlab-ce!31384
|
|
|
|
This is just in case the creation of this index takes
a while to create.
|
|
Per https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31384, this
appears to drop the runtime of the query from 1.2 ms (cold), 500ms (warm
cache) to < 20 ms.
|
|
Also removes unnecessary methods causing extra queries
|
|
|
|
`allow_local_requests_for_hooks_and_services` was renamed to
`allow_local_requests_for_web_hooks_and_services`.
|
|
Simplify SystemHookUrlValidator to inherit from PublicUrlValidator
Refactor specs to move out shared examples to be used in both
system hooks and public url validators.
|
|
|
|
This MR adds new application setting to network section
`allow_local_requests_from_system_hooks`. Prior to this change
system hooks were allowed to do local network requests by default
and we are adding an ability for admins to control it.
|
|
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14520
|
|
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3809
See merge request gitlab-org/gitlab-ce!31375
|
|
Introducing Docker Registry replication
|
|
This implements the support for `needs:` keyword
as part of GitLab CI. That makes some of the jobs
to be run out of order.
|
|
- DB migration of board milestone values
- issue finder & spec updates
|
|
For customers with thousands of entries in the table, lookups for an
LDAP identity dominated the PostgreSQL statistics because of sequential
scans. We can speed this up by adding a partial index with the
extern_uid and provider.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59630
|
|
|
|
These migrations do the following:
- Adds a new `issue_id` column to `versions`. This fixes an n+1 problem
when loading versions for an issue in GraphQL as AR can now load from
cache
- Change the unique restraint on versions.sha to be scoped to `issue_id`
as in order to import version data, we need to allow duplicate `sha`
values for versions
- Update all versions with an `issue_id`
https://gitlab.com/gitlab-org/gitlab-ee/issues/11090
|
|
Adds Job specific variables to facilitate specifying variables when
running manual jobs.
|
|
This MR updates the y_label values and the label
values in common_metrics and cluster_metrics to
append the units of measurement to the labels.
|
|
Adds event enum column to DesignsVersions join table
See merge request gitlab-org/gitlab-ce!30745
|
|
It needs to default to an empty array logically.
|
|
`Array.reverse_each` is faster than `Array.reverse.each` because:
* reverse.each creates a new array then loops each element
* reverse_each loops in reverse order (no intermediate array created)
|
|
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14597
See merge request gitlab-org/gitlab-ce!30520
|
|
Also adds index to support scopes and queries
This supports https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14656
|
|
* Limits raw requests to 300 per minute and per raw path.
* Add a new attribute to ApplicationSettings so user can change this
value on their instance.
* Uses Gitlab::ActionRateLimiter to limit the raw requests.
* Add a new method into ActionRateLimiter to log the event into auth.log
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/48717
|
|
Signed-off-by: Istvan szalai <istvan.szalai@savoirfairelinux.com>
|
|
This is the first part of Docker Registry replication
for secondary Geo node.
|
|
Remove dead mysql code
Closes #63191
See merge request gitlab-org/gitlab-ce!29608
|
|
None of this code can be reached any more, so it can all be removed
|
|
This is no longer needed with Rails 5.2. opclass is the attribute used
per https://github.com/rails/rails/pull/19090/files.
Now that we've removed the monkey patch and restored the Rails schema
dumper, it appears Rails has dropped the inclusion of `using: :btree` as
well (https://github.com/rails/rails/pull/27981).
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64529
|
|
Add index for issues on relative position, project, and state for manual sorting
See merge request gitlab-org/gitlab-ce!30542
|
|
We also scope the `rescue`s to only those raised by ActiveRecord, which
would have allowed us to spot this logic error sooner.
|