0fc9f9d3e7
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
29 lines
838 B
Ruby
29 lines
838 B
Ruby
# frozen_string_literal: true
|
|
|
|
class AddStatusToDeployments < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DEPLOYMENT_STATUS_SUCCESS = 2 # Equivalent to Deployment.state_machine.states['success'].value
|
|
|
|
DOWNTIME = false
|
|
|
|
disable_ddl_transaction!
|
|
|
|
##
|
|
# NOTE:
|
|
# Ideally, `status` column should not have default value because it should be leveraged by state machine (i.e. application level).
|
|
# However, we have to use the default value for avoiding `NOT NULL` violation during the transition period.
|
|
# The default value should be removed in the future release.
|
|
def up
|
|
add_column_with_default(:deployments,
|
|
:status,
|
|
:integer,
|
|
limit: 2,
|
|
default: DEPLOYMENT_STATUS_SUCCESS,
|
|
allow_null: false)
|
|
end
|
|
|
|
def down
|
|
remove_column(:deployments, :status)
|
|
end
|
|
end
|