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
26 lines
964 B
Ruby
26 lines
964 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
class AddDeployments < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
def change
|
|
create_table :deployments, force: true do |t|
|
|
t.integer :iid, null: false
|
|
t.integer :project_id, null: false
|
|
t.integer :environment_id, null: false
|
|
t.string :ref, null: false
|
|
t.boolean :tag, null: false
|
|
t.string :sha, null: false
|
|
t.integer :user_id
|
|
t.integer :deployable_id
|
|
t.string :deployable_type
|
|
t.datetime :created_at
|
|
t.datetime :updated_at
|
|
end
|
|
|
|
add_index :deployments, :project_id
|
|
add_index :deployments, [:project_id, :iid], unique: true
|
|
add_index :deployments, [:project_id, :environment_id]
|
|
add_index :deployments, [:project_id, :environment_id, :iid]
|
|
end
|
|
end
|