Travis does not make build information available between stages or jobs. To do this you are required to use an external service (like S3). ideally - to ensure that the binary results of the build are re-used in the docker stage (i.e. we deploy exactly what was tested) we will need to preserve the build artefacts for re-use in the docker and deploy stages.
Travis does not make build information available between stages or jobs. To do this you are required to use an external service (like S3). ideally - to ensure that the binary results of the build are re-used in the docker stage (i.e. we deploy exactly what was tested) we will need to preserve the build artefacts for re-use in the docker and deploy stages.