Skip to content

Fix S3 and packagecloud uploads step in release process

Tomasz Maczukin requested to merge fix/release-uploads into master

What does this MR do?

Fixes the error when artifacts uploaded to S3 have bigger size than the default --max-size value for travis-ci/artifacts tool. Also it splits S3 and packagecloud uploads to two separate builds, so it'll be easier to retry a failed build in some cases.

Why was this MR needed?

To improve process of releasing artifacts to S3 and packagecloud.

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 #2072 (closed)

Merge request reports