To workaround, CircleCI limitation [1]:
"Please note that since we do not support parallel deployment, specifying
‘parallel:true’ in the deployment phase will cause an error."
This commit moves the deployment step as the last action of the test
step. Doing so will ensure, every container will take care of pushing
images it was responsible to build.
[1] https://circleci.com/docs/parallel-manual-setup/#simple-example
* style: Rename TASK to STEP
* do not pull base image after it was copied from node0 and loaded.
It caused the current Dockerfile to be out-of-sync with the current image.
* do not pull images after loading the downloaded and up-to-date
base.tar. It was overwriting the base.tar downloaded and loaded.
* save debian:jessie into base.tar
* use "time" command to help identify long running operation
* rename marker file from "BASE_READY" to "BASE_AVAILABLE"
* build base image only if needed.
Waiting we address the timeout of command after 120min when using
parallel containers, this reverts commit e120e368249eb5edbdbeaa665fba3b536d20a73d, reversing
changes made to 6a4826a8dfde66bc2fb7206c5293af4d38ed19ad.
Issue has been reported to CircleCI support as
https://circleci.zendesk.com/hc/en-us/requests/13273
