gitlab-org--gitlab-foss

Commit Graph

Author	SHA1	Message	Date
Lin Jen-Shin	0ab6469187	Grant privileges after database is created Never drop the database when granting privileges	2018-05-16 21:52:08 +08:00
Stan Hu	ad88e3f88d	Fix `rake db:seed_fu` not doing anything in CI The default behavior of seed_fu is to load the fixtures using the RAILS_ENV environment. In CI, since we set RAILS_ENV=test, nothing is ever loaded. Instead of `rake db:seed_fu`, use `rake gitlab:setup`, which sets up MySQL properly with limits. Closes #41517	2018-01-02 12:44:51 -08:00
Stan Hu	8efdf75bcb	Use a non-superuser user to access GitLab to ensure permissions are proper We have run into permission issues with MySQL triggers in #36633 that would have been caught earlier either if our migration tests or GitLab QA tests had been testing against non-superuser users. This change creates a non-superuser that has access to the GitLab test database and uses that. Closes #39932	2017-11-09 22:14:03 -08:00

Author

SHA1

Message

Date

Lin Jen-Shin

0ab6469187

Grant privileges after database is created

Never drop the database when granting privileges

2018-05-16 21:52:08 +08:00

Stan Hu

ad88e3f88d

Fix `rake db:seed_fu` not doing anything in CI

The default behavior of seed_fu is to load the fixtures using the RAILS_ENV
environment.  In CI, since we set RAILS_ENV=test, nothing is ever
loaded. Instead of `rake db:seed_fu`, use `rake gitlab:setup`, which sets up
MySQL properly with limits.

Closes #41517

2018-01-02 12:44:51 -08:00

Stan Hu

8efdf75bcb

Use a non-superuser user to access GitLab to ensure permissions are proper

We have run into permission issues with MySQL triggers in #36633 that
would have been caught earlier either if our migration tests or GitLab QA
tests had been testing against non-superuser users. This change creates
a non-superuser that has access to the GitLab test database and uses that.

Closes #39932

2017-11-09 22:14:03 -08:00

3 Commits