| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| | |
Reorganize indexes for the "deployments" table
Closes #36877
See merge request gitlab-org/gitlab-ce!14348
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the need for a default scope that adds a "WHERE project_id
= X" clause. This commit also includes an additional index for
Environment#last_deployment, ensuring this query uses just an index scan
instead of also applying a Filter.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36877
|
|\ \
| | |
| | |
| | |
| | | |
Fix regular expression used for opclasses to not be confused by partial index clause
See merge request gitlab-org/gitlab-ce!14343
|
| |/
| |
| |
| | |
index clause
|
| | |
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Clean up redirect routes that conflict with regular routes
Closes #36229
See merge request gitlab-org/gitlab-ce!13783
|
| |
| |
| |
| | |
…to stay within our query timeout of 60s. Also reduce the job interval to keep the same overall migration time of ~3.3 days.
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
| |
| | |
# Conflicts:
# db/schema.rb
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This index is required to allow fast retrieval of recent push events
without merge requests. Without this index in place the query would
lead to PostgreSQL scanning over 150 000 index entries all the time,
easily taking up between 200 and 500 milliseconds. This index
reduces the time spent in this process to around 40 milliseconds on
GitLab.com.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Constrain environment deployments to project IDs
Closes #36877
See merge request gitlab-org/gitlab-ce!14252
|
| | | |
|
| |/
| |
| | |
This reverts merge request !14240
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This file is a duplicate of a post-deploy migration and appears to have
been left in by mistake.
Looping through the Users table in a foreground migration would've been
a bad idea.
[ci skip]
|
| |\
| | |
| | |
| | |
| | | |
Revert "Merge branch 'revert-f2421b2b' into 'master'"
See merge request !14190
|
| | |
| | |
| | | |
This reverts merge request !14148
|
| |/
| |
| |
| |
| | |
This is required as otherwise newly created events will start with the
wrong ID.
|
|/ |
|
|
|
|
|
| |
'35012-navigation-add-option-to-change-navigation-color-palette' into 'master'"
This reverts merge request !13619
|
|\
| |
| |
| |
| | |
Update db schema to correspond with migrations
See merge request !14115
|
| | |
|
|\ \
| |/
| |
| | |
zj/gitlab-ce-zj-auto-devops-table
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'35012-navigation-add-option-to-change-navigation-color-palette' into 'master'
Add option to change navigation color palette
Closes #35012
See merge request !13619
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Finish migration to the new events setup
Closes #37241
See merge request !13932
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This finishes the procedure for migrating events from the old format
into the new format. Code no longer uses the old setup and the database
tables used during the migration process are swapped, with the old table
being dropped.
While the database migration can be reversed this will 1) take a lot of
time as data has to be coped around 2) won't restore data in the
"events.data" column as we have no way of restoring this.
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Update schema.rb from db:migrate and fix invalid index check
See merge request !14107
|
| | | | |
| | | | |
| | | | |
| | | | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
|\ \ \ \ \
| |/ / / / |
|
| | |_|/
| |/| | |
|
| | | | |
|
|\ \ \ \
| |/ / /
| | | |
| | | | |
zj/gitlab-ce-zj-auto-devops-table
|
| | | | |
|
|\ \ \ \
| |/ / / |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | |/
| |/|
| | |
| | | |
discussion resolution
|
| |\ \
| | |/
| | |
| | | |
# Conflicts:
# db/schema.rb
|
| | |
| | |
| | |
| | |
| | | |
as we destroy all gpg_signatures we don't need to downcase the email
addresses anymore.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This is faster for the deployment process, as the destroyed signatures
will be re-generated on demand again, instead of updating them all on
deploy.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To avoid having to implement legacy code handling for the obsolete
`verified_signature` attribute and to avoid any race conditions during
the zero-downtime-deployment we do the following:
1. Destroy all records
2. Migration: Use add_column_with_default to add the new attribute and
update the verification_status values on records created between 1.
and 2.
3. Deploy the new code
4. Post migration: Destroy all records
Like this we make sure that at no point there is a record with a `nil`
value for the new `verification_status` attribute.
|
| | | |
|