| Age | Commit message (Collapse) | Author |
|---|
|
Prevent EE backport migrations from running if CE is not migrated
Closes #63612
See merge request gitlab-org/gitlab-ce!30002
(cherry picked from commit 34df0b303eed0cee83d8c0ec6178d3c575a0b555)
1b063778 Prevent EE backport migrations from running if CE is not migrated
|
|
|
|
Backport approval MR rules report_type migration to CE
See merge request gitlab-org/gitlab-ce!29766
(cherry picked from commit 53036a5bc6dcdc120ce828e3366be8b4486f9a6a)
5d76e091 Backport approval MR rules report_type migration to CE
|
|
Add index to events and audit_events tables
Closes gitlab-com/Product#309
See merge request gitlab-org/gitlab-ce!29194
|
|
Migrate Kubernetes service integration templates to clusters
See merge request gitlab-org/gitlab-ce!28534
|
|
Index on created_at, author_id
|
|
Add index on invite-email to members
See merge request gitlab-org/gitlab-ce!29768
|
|
Cherry-picking the schema backport commits led to these changes being
thrown away, without this being clear.
|
|
This backports all EE schema changes to CE, including EE migrations,
ensuring both use the same schema.
== Updated tests
A spec related to ghost and support bot users had to be modified to make
it pass. The spec in question assumes that the "support_bot" column
exists when defining the spec. In the single codebase setup this is not
the case, as the column is backported in a later migration. Any attempt
to use a different schema version or use of "around" blocks to
conditionally disable specs won't help, as reverting the backport
migration would also drop the "support_bot" column. Removing the
"support_bot" tests entirely appears to be the only solution.
We also need to update some foreign key tests now that we have
backported the EE columns. Fortunately, these changes are very minor.
== Backporting migrations
This commit moves EE specific migrations (except those for the Geo
tracking database) and related files to CE, and also removes any traces
of the ee/db directory.
Some migrations had to be modified or removed, as they no longer work
with the schema being backported. These migrations were all quite old,
so we opted for removing them where modifying them would take too much
time and effort.
Some old migrations were modified in EE, while also existing in CE. In
these cases we took the EE code, and in one case removed them entirely.
It's not worth spending time trying to merge these changes somehow as we
plan to remove old migrations around the release of 12.0, see
https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
|
|
updated documentation for Geo
|
|
|
|
Backport the EE schema to CE
Closes gitlab-ee#9686
See merge request gitlab-org/gitlab-ce!26940
|
|
|
|
This backports all EE schema changes to CE, including EE migrations,
ensuring both use the same schema.
== Updated tests
A spec related to ghost and support bot users had to be modified to make
it pass. The spec in question assumes that the "support_bot" column
exists when defining the spec. In the single codebase setup this is not
the case, as the column is backported in a later migration. Any attempt
to use a different schema version or use of "around" blocks to
conditionally disable specs won't help, as reverting the backport
migration would also drop the "support_bot" column. Removing the
"support_bot" tests entirely appears to be the only solution.
We also need to update some foreign key tests now that we have
backported the EE columns. Fortunately, these changes are very minor.
== Backporting migrations
This commit moves EE specific migrations (except those for the Geo
tracking database) and related files to CE, and also removes any traces
of the ee/db directory.
Some migrations had to be modified or removed, as they no longer work
with the schema being backported. These migrations were all quite old,
so we opted for removing them where modifying them would take too much
time and effort.
Some old migrations were modified in EE, while also existing in CE. In
these cases we took the EE code, and in one case removed them entirely.
It's not worth spending time trying to merge these changes somehow as we
plan to remove old migrations around the release of 12.0, see
https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
|
|
Create models for issue trackers data
See merge request gitlab-org/gitlab-ce!28598
|
|
This backports to CE changes that allow the recording of the
repository_type in the table lfs_objects_projects.
This is in order to allow future pruning of unreferenced LFS objects,
as we will need to know which repository to look in for the LFS pointer
file.
The EE MR that contains the original code and a full explanation of the
changes is
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894
EE Issue https://gitlab.com/gitlab-org/gitlab-ee/issues/9490
Note that there was a lot of CE code changed in the EE MR because we
want to allow the wiki repository to also use LFS. See
https://gitlab.com/gitlab-org/gitlab-ce/issues/43721. As the wiki is
an unlicensed feature, a full backport is required to enable this.
|
|
EE migration port: add app-wide LDAP membership lock field
See merge request gitlab-org/gitlab-ce!29302
|
|
|
|
- create tables for storing issue trackers properties
- add model and basic logic & spec
|
|
Clean up issue-62684
Update issue-62684 changelog
Update down migrate for issue-62684
|
|
|
|
Fix null source_project_id in pool_repositories
Closes gitaly#1653
See merge request gitlab-org/gitlab-ce!29157
|
|
Due to a bug, some pool_repositories in production have a null
source_project_id column. This migration aims to fix those rows.
|
|
|
|
In order to optimize the query performance, we should use target
project id and target branch intead of cross-joining merge_requests
table.
Fix schema
Fix schema
|
|
|
|
This reverts commit fd19f887dfeeeedb483c4a4fb32f9f768e89389c, reversing
changes made to abb2d4c601d796339c8d7cb0c00946696730f198.
|
|
Add project level git depth setting
Closes #59688
See merge request gitlab-org/gitlab-ce!28919
|
|
Migrate legacy uploads
Closes #57217
See merge request gitlab-org/gitlab-ce!24679
|
|
Save certificate validity time for pages domains on save
Fill validity time for existing pages domains in background migration
|
|
Extract acme double to helper
Create ACME challanges for pages domains
* Create order & challange through API
* save them to database
* request challenge validation
We're saving order and challenge as one entity,
that wouldn't be correct if we would order certificates for
several domains simultaneously, but we always order certificate
per domain
Add controller for processing acme challenges redirected from pages
Don't save acme challenge url - we don't use it
Validate acme challenge attributes
Encrypt private_key in acme orders
|
|
This reverts merge request !28743
|
|
Uploads coming from AttachmentUploader
need to be moved to the currently supported location
(FileUploader)
|
|
Save certificate validity time for pages domains on save
Fill validity time for existing pages domains in background migration
|
|
Introduce default_git_depth in project's CI/CD settings and set it to
50. Use it if there is no GIT_DEPTH variable specified. Apply this
default only to newly created projects and keep it nil for old ones
in order to not break pipelines that rely on non-shallow clones.
default_git_depth can be updated from CI/CD Settings in the UI, must be
either nil or integer between 0 and 1000 (incl).
Inherit default_git_depth from the origin project when forking projects.
MR pipelines are run on a MR ref (refs/merge-requests/:iid/merge) and it
contains unique commit (i.e. merge commit) which doesn't exist in the
other branch/tags refs. We need to add it cause otherwise it may break
pipelines for old projects that have already enabled Pipelines for merge
results and have git depth 0.
Document new default_git_depth project CI/CD setting
|
|
|
|
When a Group is missing a route, the migration failed previously with a
`Invalid single-table inheritance type` error. To fix this, we can
disable STI for the migration class because we don't need to know about
the type to do this migration. Besides, currently Group is the only type
used in the type column.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58714
|
|
Reset merge status from mergeable MRs
See merge request gitlab-org/gitlab-ce!28843
|
|
Adds migrations to reset the merge_status of opened,
mergeable MRs. That's required by
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28513
so we're able to sync the status update along merge-ref,
without leaving MRs with a stale merge-ref.
|
|
Removes project_auto_devops#domain column
Closes #56959
See merge request gitlab-org/gitlab-ce!28574
|
|
|
|
only the year can trip 'start_date_should_be_less_than_due_date'
|
|
Now it defaults to 0
|
|
Remove migration generating lets encrypt key
Don't generate private_key if database is readonly
For reference:
This reverts commit 988a7f70489b99383b95e9f271a2caf6bb5b3a44.
This reverts commit 21acbe531592d55caf0e5b8716a3b551dafd6233.
|
|
Now that the column is ignored, we can safely drop the column
|
|
|
|
Assume that if an instance level cluster already exists, then the
KubernetesService was not being used, but allow the admin to re-enable
it if required
|
|
The migration uses active record model stubs so that field encryption
can be more easily used.
|
|
|
|
Storing this key in secrets.yml was a bad idea,
it would require users using HA setups to manually
replicate secrets across nodes during update,
it also needed support from omnibus package
* Revert "Generate Let's Encrypt private key"
This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976.
* Add Let's Encrypt private key to settings
as encrypted attribute
* Generate Let's Encrypt private key
in database migration
|
