Failed after activate new release is confusing #95
Labels
Comments
REBELinBLUE
added a commit
that referenced
this issue
Sep 17, 2015
REBELinBLUE
added a commit
that referenced
this issue
Sep 17, 2015
* master: (29 commits) Clean up DB migration to add the additional status to deployments, horrible! Added status to model #95 Add a "Finished with errors" status for deployments which fail after activation for issue #95 Updated dependencies Updated dependencies Remove whitespace Adding missing trait Updating to Laravel 5.1.11 to make sure of the Authorization feature Removing unneeded folder Updating dependencies Fixes #88 Fixes #90 By including deleted commands in the associations for DeployStep Fixes #87 by removing the builds_to_keep from pagination Updated dependencies Fix the namespace for broadcast events Fix #69 by adding a the ability to define optional commands to default to on Updating list of service providers for optimizing Fixing the compiled path for laravel 5.0.16 Typo ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After a release is activated if a step fails the status should be something like "Finished with errors" rather than "Failed" as the release is actually live
The text was updated successfully, but these errors were encountered: