Finalization is not an error scenario
@ess is already working on this.
Since Oct 1, 2018.
Assessment
This issue has not been assessed yet.
Description
At present, a failure in deploy finalization is treated as a critical failure.
The thing is, finalization is just removing artifacts from previous releases. That's not really a failure case, but more of a "log a warning and return success" case.
- Dominant language
- Ruby
- Stars
- 62
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from engineyard/engineyard-serverside
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug
engineyard/engineyard-serverside#188 · 1 assignee ·
-
backlog feature
engineyard/engineyard-serverside#178 · 1 assignee ·
-
backlog feature
engineyard/engineyard-serverside#170 · 1 assignee ·
-
feature in progress
engineyard/engineyard-serverside#167 · 1 assignee ·
All issues in engineyard/engineyard-serverside
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
TheOdinProject/curriculum#31408 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
notch8/utk_knapsack#148 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Homebrew/homebrew-cask#288729 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100