debian-mirror-gitlab/lib/tasks/dev.rake

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

92 lines
3.2 KiB
Ruby
Raw Normal View History

2021-03-11 19:13:27 +05:30
# frozen_string_literal: true
2014-09-02 18:07:02 +05:30
task dev: ["dev:setup"]
namespace :dev do
2020-03-13 15:44:24 +05:30
desc "GitLab | Dev | Setup developer environment (db, fixtures)"
2017-08-17 22:00:37 +05:30
task setup: :environment do
2014-09-02 18:07:02 +05:30
ENV['force'] = 'yes'
Rake::Task["gitlab:setup"].invoke
2019-12-26 22:10:19 +05:30
2022-05-07 20:08:51 +05:30
Gitlab::Database::EachDatabase.each_database_connection do |connection|
# Make sure DB statistics are up to date.
2022-06-21 17:19:12 +05:30
# gitlab:setup task can insert quite a bit of data, especially with MASS_INSERT=1
# so ANALYZE can take more than default 15s statement timeout. This being a dev task,
# we disable the statement timeout for ANALYZE to run and enable it back afterwards.
connection.execute('SET statement_timeout TO 0')
2022-05-07 20:08:51 +05:30
connection.execute('ANALYZE')
2022-06-21 17:19:12 +05:30
connection.execute('RESET statement_timeout')
2022-05-07 20:08:51 +05:30
end
2019-12-26 22:10:19 +05:30
2014-09-02 18:07:02 +05:30
Rake::Task["gitlab:shell:setup"].invoke
end
2018-03-17 18:26:18 +05:30
2020-03-13 15:44:24 +05:30
desc "GitLab | Dev | Eager load application"
2018-03-17 18:26:18 +05:30
task load: :environment do
2019-07-07 11:18:12 +05:30
Rails.configuration.eager_load = true
2018-03-17 18:26:18 +05:30
Rails.application.eager_load!
end
2022-06-21 17:19:12 +05:30
# If there are any clients connected to the DB, PostgreSQL won't let
# you drop the database. It's possible that Sidekiq, Puma, or
# some other client will be hanging onto a connection, preventing
# the DROP DATABASE from working. To workaround this problem, this
# method terminates all the connections so that a subsequent DROP
# will work.
desc "Used to drop all connections in development"
task :terminate_all_connections do
# In production, we might want to prevent ourselves from shooting
# ourselves in the foot, so let's only do this in a test or
# development environment.
unless Rails.env.production?
cmd = <<~SQL
SELECT pg_terminate_backend(pg_stat_activity.pid)
FROM pg_stat_activity
WHERE datname = current_database()
AND pid <> pg_backend_pid();
SQL
Gitlab::Database::EachDatabase.each_database_connection(include_shared: false) do |connection|
connection.execute(cmd)
rescue ActiveRecord::NoDatabaseError
end
end
end
databases = ActiveRecord::Tasks::DatabaseTasks.setup_initial_database_yaml
namespace :copy_db do
ALLOWED_DATABASES = %w[ci].freeze
2022-07-16 23:28:13 +05:30
defined_copy_db_tasks = []
2022-06-21 17:19:12 +05:30
ActiveRecord::Tasks::DatabaseTasks.for_each(databases) do |name|
next unless ALLOWED_DATABASES.include?(name)
2022-07-16 23:28:13 +05:30
defined_copy_db_tasks << name
2022-06-21 17:19:12 +05:30
desc "Copies the #{name} database from the main database"
task name => :environment do
Rake::Task["dev:terminate_all_connections"].invoke
db_config = ActiveRecord::Base.configurations.configs_for(env_name: Rails.env, name: name)
ApplicationRecord.connection.create_database(db_config.database, template: ApplicationRecord.connection_db_config.database)
rescue ActiveRecord::DatabaseAlreadyExists
warn "Database '#{db_config.database}' already exists"
end
end
2022-07-16 23:28:13 +05:30
ALLOWED_DATABASES.each do |name|
next if defined_copy_db_tasks.include?(name)
# :nocov: we cannot mock ActiveRecord::Tasks::DatabaseTasks in time
# Workaround for GDK issue, see
# https://gitlab.com/gitlab-org/gitlab-development-kit/-/issues/1464
desc "No-op task"
task name
# :nocov:
end
2022-06-21 17:19:12 +05:30
end
2014-09-02 18:07:02 +05:30
end