summaryrefslogtreecommitdiff
path: root/db/migrate/20160504112519_add_run_untagged_to_ci_runner.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add version 4.2 to all existing migrationsjprovazn-versioned-migrationsJan Provaznik2018-11-221-1/+1
| | | | | | | | | 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
* Enable rubocop for db/**/* and ee/db/**/*49582-enable-cops-for-dbLin Jen-Shin2018-07-251-1/+0
|
* Enable RuboCop for migrationsenable-rubocop-for-migrationsSean McGivern2016-06-091-0/+1
| | | | | | | Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file.
* Use migration helper to prevent downtime migrationfeature/runner-config-untagged-jobsGrzegorz Bizon2016-05-191-8/+10
|
* Add not null constraint to run untagged runner optionGrzegorz Bizon2016-05-191-1/+1
|
* Add runner db field for ability to run untagged jobsGrzegorz Bizon2016-05-191-0/+11