de746b4004
Based on the configuration recommended by Knapsack PRO [1] and Pronto [2]. So far there are a few issues: * Bundled gems don't seem to be cached * The Ruby version can't be read from .ruby-version and needs to be set manually * Tests are slower than when run on Github Actions or Travis CI * There seem to be many flaky tests, maybe because tests are slower (this might actually help us fixing flaky bugs or performance bottlenecks) An advantage of Gitlab CI is we can access the screenshots taken when a system test fails. [1] https://docs.knapsackpro.com/2019/how-to-run-parallel-jobs-for-rspec-tests-on-gitlab-ci-pipeline-and-speed-up-ruby-javascript-testing [2] https://github.com/prontolabs/pronto/#gitlab-integration
12 lines
164 B
Plaintext
12 lines
164 B
Plaintext
default: &default
|
|
adapter: postgresql
|
|
encoding: unicode
|
|
host: postgres
|
|
pool: 5
|
|
username: consul
|
|
password:
|
|
|
|
test:
|
|
<<: *default
|
|
database: consul_test
|