Only call dev:copy_db:ci when necessary
Overview
We added no-op dev:copy_db:ci
task when the ci
database is not configured
The issue is that we call dev:copy_db:ci
on gdk update
, and gdk reconfigure
. (see !2496 (comment 916075367) for background)
- It should only be called on
gdk reconfigure
. It is not guaranteed for theci
database to be configured ingitlab/config/database.yml
when runninggdk update
as the user needs to rungdk reconfigure
to change that file. - Once the first step is done, we can remove the no-op task from GitLab
Steps to replicate (optional)
Proposal (optional)
Environment (optional)
- Operating system name:
<!-- output of `uname -a` command -->
- Architecture:
<!-- output of `arch` command -->
- The contents of your
gdk.yml
(if any) - Ruby version:
<!-- output of `ruby --version` command -->
- GDK version:
<!-- output of `git rev-parse --short HEAD` command -->
Edited by Thong Kuah