delta/gitlab/gitlab-ce.git/scripts/create_mysql_user.sh, branch 44296-commit-path gitlab.com: gitlab-org/gitlab-ce.git Fix `rake db:seed_fu` not doing anything in CI 2018-01-02T20:44:51+00:00 Stan Hu stanhu@gmail.com 2017-12-27T13:41:28+00:00 ad88e3f88d2ac287f5a95952f95da4feae90944e 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 
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
Use a non-superuser user to access GitLab to ensure permissions are proper 2017-11-10T06:14:03+00:00 Stan Hu stanhu@gmail.com 2017-11-09T20:18:26+00:00 8efdf75bcb3621822523803b02bd308792bf84d5 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 
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