ajgon / opsworks_ruby

100%

master: 100%

LAST BUILD ON BRANCH fix/156

branch: fix/156

CHANGE BRANCH

x

Reset

• fix/156
• 1.9.1
• chore/fix-docker
• dependabot/bundler/activesupport-5.2.4.3
• dependabot/bundler/rack-2.0.8
• dependabot/bundler/rack-2.2.3
• dependabot/bundler/rexml-3.2.5
• encrypted-travis
• entryboss-master
• feat/165
• feat/apache2-mod-status
• feat/chef-version
• feat/force-ssl
• feat/foreground-appserver
• feat/fullstaq
• feat/multiple-databases-support
• feat/packs-webserver
• feat/remove-deployer
• feat/webpacker
• fix/127
• fix/157
• fix/167
• fix/224
• fix/92
• fix/include-deploy-resource
• integration
• master
• ruzia-fix_puma_service
• sidekiq/multiple-configs
• v0.1.0
• v0.10.0
• v0.2.0
• v0.2.1
• v0.3.0
• v0.3.1
• v0.5.0
• v0.6.0
• v0.7.0
• v0.8.0
• v1.0.0
• v1.1.0
• v1.1.1
• v1.1.2
• v1.10.0
• v1.10.1
• v1.11.0
• v1.12.0
• v1.13.0
• v1.14.0
• v1.15.0
• v1.16.0
• v1.17.0
• v1.18.0
• v1.18.1
• v1.19.0
• v1.2.0
• v1.2.1
• v1.20.0
• v1.20.1
• v1.20.2
• v1.20.3
• v1.3.0
• v1.4.0
• v1.5.0
• v1.6.0
• v1.7.0
• v1.7.1
• v1.8.0
• v1.9.0
• v1.9.1
• wip/http
• wip/s3

Build # 437

Build Type

push

travis-ci

Committed by ajgon

Commit Message

feat(ruby): introduced new `ruby-version` JSON parameter.

This removes a misleading `ruby-ng.ruby_version` paramater in favor of
new universal `ruby-version`. The problem was, that the old one was used
for both distributions (Ubuntu and Amazon Linux) while in fact,
`ruby-ng` was referring to Ubuntu-only cookbook.

The new parameter is distro-agnostic and cookbook-agnostic, clearly
speaking it's intention.

Resolves #156

BREAKING CHANGE: If you were using `ruby-ng.ruby_version` JSON
configuration parameter in your stack/layer configuration, please change
it to `ruby-version`. Since `ruby-version` is set by default to the
freshest version of ruby available, you may end up with unexpected
upgrade of ruby on your system.

Run Details

1690 of 1690 relevant lines covered (100.0%)

25.7 hits per line