David Michael Nelson f79a386aad Prevents last good release from being deleted on cleanup (#1922) ... * Prevents last good release from being deleted on cleanup Issue: 1907 If there are many failed deployments the relese folders will still be left there and eventually if deploy:cleanup is executed it will delete the release that is referenced by the "current" symlink, potentially causing downtime. That change will prevent the "current release" from ever being removed during cleanup. * Link PR on CHANGELOG * Verify if current dir exists Check if current release directory exists instead of relying on exceptions being raised.		2017-10-12 12:40:57 -07:00
..
step_definitions	Prevents last good release from being deleted on cleanup (#1922)	2017-10-12 12:40:57 -07:00
support	Adds acceptance test for rollback feature. (#1891)	2017-07-04 19:02:58 -07:00
configuration.feature	Fix cucumber spec for loading tasks from stage configs	2014-12-10 01:13:19 +03:00
deploy.feature	Prevents last good release from being deleted on cleanup (#1922)	2017-10-12 12:40:57 -07:00
deploy_failure.feature	Add hook for deploy failure	2013-11-01 12:24:36 +00:00
doctor.feature	Add doctor:variables, :environment, and :gems	2016-04-25 17:14:55 +02:00
installation.feature	Allow cap -T to work when no Capfile is present	2017-03-19 20:12:19 -07:00
sshconnect.feature	Improve Cucumber tests	2015-02-14 11:32:45 -08:00
stage_failure.feature	Raise if a stage has an invalid name like "deploy"	2016-05-21 11:55:57 -07:00
subdirectory.feature	Allow cap to be run within subdir and still work	2017-03-06 07:33:47 -08:00