gitlab-org--gitlab-foss/db/migrate/20170824101926_add_auto_dev...

class AddAutoDevopsEnabledToApplicationSettings < ActiveRecord::Migration[4.2]
  include Gitlab::Database::MigrationHelpers

  DOWNTIME = false

  disable_ddl_transaction!

  def up
    add_column_with_default(:application_settings, :auto_devops_enabled, :boolean, default: false)
  end

  def down
    remove_column(:application_settings, :auto_devops_enabled, :boolean)
  end
end
Add version 4.2 to all existing migrations DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912 2018-11-13 07:27:31 +00:00			`class AddAutoDevopsEnabledToApplicationSettings < ActiveRecord::Migration[4.2]`
Implement the implied CI/CD config for AutoDevOps Behind an application setting, which defaults to false, this commit implements the implied CI/CD config. Which means that in the case we can't find the `.gitlab-ci.yml` on the commit we want to start a pipeline for, we fall back to an implied configuration. For now the Bash template has been copied to `Auto-Devops.gitlab-ci.yml` so the tests actually work. Fixes #34777 2017-08-24 11:01:33 +00:00			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

			`disable_ddl_transaction!`

			`def up`
			`add_column_with_default(:application_settings, :auto_devops_enabled, :boolean, default: false)`
			`end`

			`def down`
			`remove_column(:application_settings, :auto_devops_enabled, :boolean)`
			`end`
			`end`