- Mar 22, 2020
-
-
GitLab Bot authored
-
- Jan 23, 2020
-
-
GitLab Bot authored
-
- Jul 29, 2019
-
-
Yorick Peterse authored
This backport changes made by EE to the files in the scripts/ directory. This comes with a few changes to some scripts to make them work in the single codebase setup.
-
- Jul 25, 2019
-
-
Heinrich Lee Yu authored
Changes all calls to data_source_exists? to table_exists? since that is the intent of these calls
-
- Jul 23, 2019
-
-
Nick Thomas authored
None of this code can be reached any more, so it can all be removed
-
- Jun 25, 2019
-
-
DJ Mountney authored
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
-
DJ Mountney authored
Set the mininum supported migration version to be the schema version as of 11.11.0, and errors you if that is not detected during gitlab:db:configure
-
- Apr 02, 2019
-
-
Wei-Meng Lee authored
-
- Feb 06, 2019
-
-
Jose Torres authored
This adds a conditional statement before truncating the `schema_migrations` table. This comit also ports this code to Rails 5.
-
- Sep 12, 2018
-
-
DJ Mountney authored
If doing a schema load, the post_migrations should also be marked as up, even if SKIP_POST_DEPLOYMENT_MIGRATIONS was set, otherwise future migration runs will be broken.
-
- Jun 27, 2018
-
-
DJ Mountney authored
If you called rake gitlab:db:drop_tables before running gitlab-ctl reconfigure (or rake gitlab:db:configure)
-
- May 03, 2017
-
-
Nick Thomas authored
-
- Mar 08, 2017
-
-
Douwe Maan authored
-
- Feb 23, 2017
-
-
Douwe Maan authored
-
- Jul 26, 2016
-
-
Drew Blessing authored
-
- Jul 20, 2016
-
-
Yorick Peterse authored
These new checks can be used to check if migrations require downtime or not (as tagged by their authors). In CI this compares the current branch with master so migrations added by merge requests are automatically verified. To check the migrations added since a Git reference simply run: bundle exec rake gitlab:db:downtime_check[GIT_REF]
-
- Jun 09, 2016
-
-
Stan Hu authored
!4318 broke the gitlab:db:drop_tables functionality for PostgreSQL. Closes #15259
-
- Jun 03, 2016
-
-
Connor Shea authored
Colorize is a gem licensed under the GPLv2, so we can’t use it in GitLab without relicensing GitLab under the terms of the GPL. Rainbow is licensed under the MIT license and does the exact same thing as Colorize, so Rainbow was added in place of Colorize. The syntax is slightly different for Rainbow vs. Colorize, and was updated in accordance. The gem is still a dependency of Spinach, so it’s included in the development/test environments, but won’t be packaged with the actual product, and therefore doesn’t require we relicense the product. An attempt at relicensing Colorize was made, but didn’t succeed as the library owner never responded. Rainbow library: https://github.com/sickill/rainbow Relevant issue regarding licensing in GitLab's gems: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3775
-
James Lopez authored
This reverts commit 3e991230.
-
James Lopez authored
# Conflicts: # app/models/project.rb
-
- May 27, 2016
-
-
Daniel Beyer authored
closes #15259
-
- May 25, 2016
-
-
DJ Mountney authored
Switch the gitlab:db:configure task to use tables.any? instead of looking specifically for the schema_migrations table
-
DJ Mountney authored
-
DJ Mountney authored
-
- May 09, 2016
-
-
Drew Blessing authored
-
- May 03, 2016
-
-
Drew Blessing authored
-
- Mar 22, 2016
-
-
Drew Blessing authored
-