CI build has been broken for a long time. It is time to fix this.
The build was broken because latest version of rubygems
Use a 'minimal' VM to avoid issues with ruby, bundler 2.0 and the
fact that we don't use a Gemfile.lock to force the use of bundler
1.x. It is messy. I spent too much time trying to fix. It is better
to avoid all this for now and re-enable later if we need it.
Run reevoocop with docker-compose.
Disable posting code coverage results to CodeClimate. This is
temporary, until we re-enable ruby/bundler.
Remove slack notifications. We have moved to horrible and develope
unfriendly MS Teams.
Pin postgres to v9. There is an issue with rails 4.x and pg > 9.
palin
commented
4 years ago
CI build has been broken for a long time. It is time to fix this. The build was broken because latest version of rubygems
Use a 'minimal' VM to avoid issues with ruby, bundler 2.0 and the fact that we don't use a Gemfile.lock to force the use of bundler 1.x. It is messy. I spent too much time trying to fix. It is better to avoid all this for now and re-enable later if we need it.
Run reevoocop with docker-compose.
Disable posting code coverage results to CodeClimate. This is temporary, until we re-enable ruby/bundler.
Remove slack notifications. We have moved to horrible and develope unfriendly MS Teams.
Pin postgres to v9. There is an issue with rails 4.x and pg > 9.
Fix issue with missing 'require' introduced in grape > 1.25. See https://github.com/ruby-grape/grape/issues/1939
Use latest version of rails 4.x
Other minor fixes that I failed to record.