| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
- Do not care about error when creating index on PostgreSQL
- Test against PostgreSQL 9.2
|
|
|
|
|
|
| |
> Mysql2::Error: Table 'ci_builds' is specified twice, both as a target for 'UPDATE' and as a separate source for data: UPDATE `ci_builds` SET `retried` = ((SELECT MAX(ci_builds2.id)
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/32647
|
|\
| |
| |
| |
| |
| |
| | |
Fix incorrect renaming migrations
Closes #32526 and #32530
See merge request !11515
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
Closes #32469
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Check if OLD is set when migrating issue assignees
Closes #32439
See merge request !11461
|
| |
| |
| |
| |
| |
| | |
The procedure for migrating issue assignees is invoked on both an INSERT
and UPDATE. This means it will fail for INSERTs because OLD is set to
NULL in this case.
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
Rename `build_events` to `job_events`
Closes #31620
See merge request !11287
|
|\
| |
| |
| |
| |
| |
| | |
Foreign key for Pipeline schedule owner
Closes #31932
See merge request !11233
|
| |
| |
| |
| |
| |
| | |
Set to nullify, so the settings remain if the user is deleted.
Fixes gitlab-org/gitlab-ce#31932
|
| |
| |
| | |
This reverts merge request !11287
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Rename `build_events` to `job_events`
Closes #31620
See merge request !11287
|
| |/ |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Make auto-cancelling pending pipelines on by default
Closes #30656
See merge request !11023
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
add-index-for-auto_canceled_by_id-mysql
* upstream/master: (224 commits)
Added balsamiq jasmine integration test
Add support for deltas_only under Gitaly
Codestyle
Update CHANGELOG.md for 9.1.4
Update CHANGELOG.md for 9.1.4
Update CHANGELOG.md for 9.1.4
Update CHANGELOG.md for 9.1.4
Minor cosmetic fixes in hooks admin screen
Documentation for repository_update_events
Changelog
Update SystemHooks API to expose and handle new repository_update_events
Make the new repository_update_events configurable in System Hooks UI
Added repository_update hook
Wait for requests after each Spinach scenario instead of feature
Remove trailing comma in dependency linker to satisfy Rubocop
Fix specs
New branch new mr docs
Relax rake backup regex to handle CE and EE RCs
Fix conflict resolution from corrupted upstream
Removed all instances of Object.assign by using es6 classes, also includes some …
...
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Clean up ci variables table
Closes #31799
See merge request !11186
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Enforced by the database, and no callbacks need to be called.
Combined with 7b9b2c6099 and 294a8b8a6d this resolves
gitlab-org/gitlab-ce#31799
|
| | |
| | |
| | |
| | |
| | | |
Variables shouldn't exist without a project, so a foreign key was added
with CASCADE'ing effects.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
To be more specific; key, and project_id. If either of these is
NULL its wrong, because:
1. storing a key value pair without key is just plain wrong
2. all variables should belong to a project
Non of these cases existed on the staging database.
|
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Retried in database
Closes #25737
See merge request !11115
|
| | | |
|
| | | |
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'master'
Resolve "Use consistent style for trailing commas"
Closes #27144
See merge request !11063
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use the EnforcedStyleForMultiline: no_comma option.
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Since this is a cleanup, ran by a post-deploy, there is no need to lookup the
admin to run the cleanup.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Destroying projects can be very time consuming. So instead of destroying them in
the post-deploy, just schedule them and make Sidekiq do the hard work.
They are scheduled in batches of 5000 records. This way the number of database
requests is limited while also the amount data read to memory is limited.
|
| | | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There are many projects in `pending_delete` state, this post-deploy migration
cleans them up.
The script is based on https://gitlab.com/gitlab-org/gitlab-ce/snippets/1648654
and https://gitlab.com/gitlab-org/gitlab-ce/snippets/1611429. The use of these
scripts were described in
https://gitlab.com/gitlab-com/infrastructure/issues/888.
|
|\ \ \
| |/ /
| | |
| | | |
# Conflicts:
# db/schema.rb
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|