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
21 lines
668 B
Ruby
21 lines
668 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class CreateCiBuildsRunnerSession < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :ci_builds_runner_session, id: :bigserial do |t|
|
|
t.integer :build_id, null: false
|
|
t.string :url, null: false
|
|
t.string :certificate
|
|
t.string :authorization
|
|
|
|
t.foreign_key :ci_builds, column: :build_id, on_delete: :cascade
|
|
t.index :build_id, unique: true
|
|
end
|
|
end
|
|
end
|