-
Notifications
You must be signed in to change notification settings - Fork 644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't fail build if volume-clean fails. #788
Conversation
Codecov Report
@@ Coverage Diff @@
## master #788 +/- ##
============================================
- Coverage 50.98% 50.97% -0.02%
+ Complexity 1213 1212 -1
============================================
Files 140 140
Lines 7129 7129
Branches 956 956
============================================
- Hits 3635 3634 -1
Misses 3178 3178
- Partials 316 317 +1
|
Sorry, for coming back to this PR that late. However, it seems to be broken to me when you look into the list of changes and touched files. The conflicts are because we moved on, but the original changeset is still too huge to even review it. I'm going to close this PR therefore, it would be awesome if you create a new PR. Alternatively, if you describe the problem in a GitHub issue we could try to find a solution together. Again sorry for the very late response. |
This fix is admittedly simplistic. It does not take into account any of the other possible causes for an exception. However, if you are using volume-clean, chances are you're using volume-create, or many of the other goals provided by DMP. In that case, you will almost certainly receive errors pointing you at the real problem.
I cherry picked your change now, should be clean again. |
I just allowed 404 as a valid response code for a volume delete operation. This is returned when the volume does not exists. I think this is the better solution. |
Wunderbar! I'll give it a look because I finally got back to that part of the project! |
Sorry I took so long to get back to this. Yes, this definitely fixed the problem. Many Thanks! Now our developers don't have to manually clean up the old volumes! |
This fix is admittedly simplistic. It does not take into account any of the other possible causes for an exception. However, if you are using volume-clean, chances are you're using volume-create, or many of the other goals provided by DMP. In that case, you will almost certainly receive errors pointing you at the
real problem.