delta/gitlab/gitlab-ce.git/spec/migrations, branch scripts-differences

Migrations for adding issue_id to versions table

2019-07-29T18:55:19+00:00

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

Add default for outbound_local_requests_whitelist

2019-07-25T18:43:52+00:00

It needs to default to an empty array logically.

Fix wrong pages access level default

2019-07-17T12:56:58+00:00

- Set access level in before_validation hook
- Add post migration for updating existing project_features

Upgrade to Rails 5.2

2019-07-12T02:15:31+00:00

Updates changed method names and fixes spec failures

Change occurrence of Sidekiq::Testing.inline!

2019-07-03T20:02:17+00:00

- Change it to perform_enqueued_jobs

Merge branch '44990-remove-old-i' into 'master'

2019-07-03T09:19:17+00:00

Remove old migration specs that violate FactoriesInMigrationSpecs

See merge request gitlab-org/gitlab-ce!30280

Show upcoming status for releases

2019-07-03T09:12:15+00:00

Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at

Remove old migrations and specs

2019-07-02T19:55:56+00:00

This removes old migrations that violate the
FactoriesinMigrationSpecs cop

Remove migration specs from 201[4567]

2019-07-02T08:35:03+00:00

Since the migrations are gone, we don't need these specs either

Prevent EE backport migrations from running if CE is not migrated

2019-06-25T12:42:10+00:00

If a user upgraded to any GitLab 11.x EE version but switched
back to CE, it's possible the state of the EE tables are not
in the right state for the EE backport migration to work properly.
In particular, there were three tables that had trouble:

* epics
* geo_event_log
* vulnerability_feedback

The EE backport migration would fail while trying to add foreign key
constraints because a key didn't exist in the table. This happens
because any EE migration that add or removed columns between v11.0.0 and
v11.11.3 are not guaranteed to be applied in an CE installation. The EE
backport schema does not individually backport these migrations.

We now check if certain columns are present to determine whether
the backport migration is in the proper state. CE users are required
to upgrade to v11.11.3 EE if they ever installed EE previously before
they can go back to v12.x CE.

Tested via:

```
git checkout -f v11.0.0-ee
bundle exec rake db:reset
git checkout .; git checkout -f v11.11.3
bundle exec rake db:migrate
git checkout .; git checkout -f v12.0.0
bundle exec rake db:migrate

```