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
23 lines
693 B
Ruby
23 lines
693 B
Ruby
class CreateJobArtifacts < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :ci_job_artifacts do |t|
|
|
t.belongs_to :project, null: false, index: true, foreign_key: { on_delete: :cascade }
|
|
t.integer :job_id, null: false
|
|
t.integer :file_type, null: false
|
|
t.integer :size, limit: 8
|
|
|
|
t.datetime_with_timezone :created_at, null: false
|
|
t.datetime_with_timezone :updated_at, null: false
|
|
t.datetime_with_timezone :expire_at
|
|
|
|
t.string :file
|
|
|
|
t.foreign_key :ci_builds, column: :job_id, on_delete: :cascade
|
|
t.index [:job_id, :file_type], unique: true
|
|
end
|
|
end
|
|
end
|