gitlab-org--gitlab-foss/scripts/create_mysql_user.sh

#!/bin/bash

mysql --user=root --host=mysql <<EOF
CREATE DATABASE IF NOT EXISTS gitlabhq_test DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
CREATE USER IF NOT EXISTS 'gitlab'@'%';
GRANT ALL PRIVILEGES ON gitlabhq_test.* TO 'gitlab'@'%';
FLUSH PRIVILEGES;
EOF
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 15:18:26 -05:00			`#!/bin/bash`

			`mysql --user=root --host=mysql <<EOF`
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 2017-12-27 08:41:28 -05:00			`CREATE DATABASE IF NOT EXISTS gitlabhq_test DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;`
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 15:18:26 -05:00			`CREATE USER IF NOT EXISTS 'gitlab'@'%';`
			`GRANT ALL PRIVILEGES ON gitlabhq_test.* TO 'gitlab'@'%';`
			`FLUSH PRIVILEGES;`
			`EOF`