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
550 B
Ruby
21 lines
550 B
Ruby
class CreateCiTriggerSchedules < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :ci_trigger_schedules do |t|
|
|
t.integer "project_id"
|
|
t.integer "trigger_id", null: false
|
|
t.datetime "deleted_at"
|
|
t.datetime "created_at"
|
|
t.datetime "updated_at"
|
|
t.string "cron"
|
|
t.string "cron_timezone"
|
|
t.datetime "next_run_at"
|
|
end
|
|
|
|
add_index :ci_trigger_schedules, :next_run_at
|
|
add_index :ci_trigger_schedules, :project_id
|
|
end
|
|
end
|