ajgon / opsworks_ruby

100%

master: 100%

LAST BUILD ON BRANCH fix/92

branch: fix/92

CHANGE BRANCH

x

Reset

• fix/92
• 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/156
• fix/157
• fix/167
• fix/224
• 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 # 331

Build Type

push

travis-ci

Committed by ajgon

Commit Message

fix: moved all pid-related files from shared/pids to /run/lock

The main reason behind this fix is, that sometimes between server restarts,
PID files remain on the file system, causing `start` scripts to crash.
On AWS /run/lock is a special directory, designed for that, usually with tmpfs
mounted in it. This means, that after each restart this directory gets wiped out.

Fixes #92

Run Details

1463 of 1463 relevant lines covered (100.0%)

12.86 hits per line