Jan Provaznik
0fc9f9d3e7
Add version 4.2 to all existing migrations
...
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
2018-11-22 13:18:28 +01:00
Kamil Trzcinski
92e8ad5247
Merge index during table creation
2017-12-05 12:03:35 +01:00
Kamil Trzcinski
e58ce2b72e
Remove index on file_type
2017-12-04 20:21:49 +01:00
Kamil Trzcinski
0464c25f60
Store expire_at in ci_job_artifacts
2017-12-03 12:05:23 +01:00
Zeger-Jan van de Weg
ba5697fd80
Fix legacy migration test
2017-12-03 12:04:49 +01:00
Zeger-Jan van de Weg
c7d945758a
Fix most test failures
2017-12-03 12:04:49 +01:00
Zeger-Jan van de Weg
61864a5a5b
Rename Artifact to JobArtifact, split metadata out
...
Two things at ones, as there was no clean way to seperate the commit and
give me feedback from the tests.
But the model Artifact is now JobArtifact, and the table does not have a
type anymore, but the metadata is now its own model:
Ci::JobArtifactMetadata.
2017-12-03 12:04:48 +01:00
