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
698 B
Ruby
29 lines
698 B
Ruby
# rubocop:disable Migration/Timestamps
|
|
class CreatePipelineSchedulesTable < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def up
|
|
create_table :ci_pipeline_schedules do |t|
|
|
t.string :description
|
|
t.string :ref
|
|
t.string :cron
|
|
t.string :cron_timezone
|
|
t.datetime :next_run_at
|
|
t.integer :project_id
|
|
t.integer :owner_id
|
|
t.boolean :active, default: true
|
|
t.datetime :deleted_at
|
|
|
|
t.timestamps null: true
|
|
end
|
|
|
|
add_index(:ci_pipeline_schedules, :project_id)
|
|
add_index(:ci_pipeline_schedules, [:next_run_at, :active])
|
|
end
|
|
|
|
def down
|
|
drop_table :ci_pipeline_schedules
|
|
end
|
|
end
|