GitLab Bot
2f9c0a9f2c
Add latest changes from gitlab-org/gitlab@master
2023-10-11 18:11:13 +00:00
GitLab Bot
82b9539d93
Add latest changes from gitlab-org/gitlab@master
2023-09-13 15:12:03 +00:00
GitLab Bot
0548fa3575
Add latest changes from gitlab-org/gitlab@master
2023-08-01 03:08:46 +00:00
GitLab Bot
a8b96c3072
Add latest changes from gitlab-org/gitlab@master
2023-01-23 15:10:34 +00:00
GitLab Bot
0ebbf19f2d
Add latest changes from gitlab-org/gitlab@master
2021-06-08 15:10:00 +00:00
GitLab Bot
4c5468b408
Add latest changes from gitlab-org/gitlab@master
2020-06-24 15:08:50 +00:00
Thong Kuah
fbd987a977
Test schema_version_check directly
...
Testing via db:migrate causes side-effects like setting
ActiveRecord::Base.configurations and also it runs schema dump into
db/schema.rb. Rather than keep up, we test schema_version_check directly
2019-07-01 15:48:14 +12:00
Lin Jen-Shin
de0f41b4d1
Quarantine schema_version_check because tests after it failed
2019-07-01 00:47:57 +00:00
DJ Mountney
e793f96c2b
Add the frozen literal to the correct file
2019-06-25 10:44:40 -07:00
DJ Mountney
e448124fab
Add an flag for skipping the schema version check
...
If you chose to use the rollback migration feature on your current
version for example, you should still have a way to migrate, being
that you are still on a supported migration path.
2019-06-25 10:44:40 -07:00
DJ Mountney
f4e1553519
Move min schema version check to db:migrate
...
Rather than have it checked only as part of gitlab:db:configure, we will
instead have it as a pre-req for every db:migrate command
2019-06-25 10:44:40 -07:00