Split the package build and push to package server

Currently this is done in the same make do_release step. If push to packagecloud fails for some reason, we need to rebuild the package.

We should have the package upload to package server in a separate stage of the build.

We could try leveraging artifacts in our CI. We could get an artifact (package) from the previous step and upload in the separate step.

cc @twk3

Added up-for-grabs label

The downside is that we would have to wait for all the packages to be build before we would move onto the next stage, to start pushing them to packagecloud. I wonder if we could get the job to use it's own previous artifact in the case of a retry.

mentioned in issue #1356 (closed)

Milestone changed to %8.12

Milestone changed to %8.13

Milestone changed to %Backlog

We've now an instance as described, where the package was built, but a failure to upload occurred 504 Gateway Timeout, that failed to upload el, but succeeded for ol and sl.

For the time being, I am looking at doing retries in side support/packagecloud_upload.sh to handle such a case. This will not remove the possibility of separating the steps, but will address problematic uploads.

Superseded and completed via #2071 (closed). Hence, closing.

closed