Prevent caching failures from marking a build as failed (!359) · Merge requests · GitLab.org / gitlab-runner · GitLab

Do not update/delete: Banner broadcast message test data

Do not update/delete: Notification broadcast message test data

Nick Thomas requested to merge nick.thomas/gitlab-ci-multi-runner:1788-cache-failures-are-not-fatal into master Oct 19, 2016

What does this MR do?

Alters the generated shell scripts to output a warning and continue if cache upload/download

Why was this MR needed?

Caching is not guaranteed to be present, so if it fails, there is no need to fail a build that is otherwise fine.

Are there points in the code the reviewer needs to double check?

Does this MR meet the acceptance criteria?

Documentation created/updated
Tests
- Added for this feature/bug
- All builds are passing
Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

Closes #1788 (closed)

/cc @stanhu @godfat

If our cache server has a bug serving the files, that should be addressed there too, but this should keep the runner happy