Move report copy to cleanup stage to have them even in case of scan failure.
Fix #24
Explain why this change is being made.
Report were not generated when both -r and -f options were used, and when scan is failing.
Explain how this is accomplished.
I tried a lot of things, but this script is not really easy to maintain. The cleanest way I found was to move the report copy step in the cleanup stage, which is not a bad stage for that either.
Merge/Deploy Checklist
[ ] It has been reviewed for code quality.
[ ] It has been visually reviewed and accepted.
How do you manually test this?
inline_scan -p -r -f ubuntu:latest will generate reports, before and after the change.
inline_scan -p -r -f alpine:3.7 will NOT generate reports before, and it will generate reports after the change
Move report copy to cleanup stage to have them even in case of scan failure.
Fix #24
Explain why this change is being made.
Report were not generated when both -r and -f options were used, and when scan is failing.
Explain how this is accomplished.
I tried a lot of things, but this script is not really easy to maintain. The cleanest way I found was to move the report copy step in the cleanup stage, which is not a bad stage for that either.
Merge/Deploy Checklist
How do you manually test this?
inline_scan -p -r -f ubuntu:latest
will generate reports, before and after the change.inline_scan -p -r -f alpine:3.7
will NOT generate reports before, and it will generate reports after the changeScreenshots