Closed MikeTheCanuck closed 7 years ago
On the basis of my latest build, I have to believe that this error is getting in the way of my deploy.
In Travis build 216 on line 432-444, I see no other errors until "ERROR: New task definition not running within 90 seconds", and until I have evidence otherwise, I'd guess this is because we're not actually successfully upload the new container image, so that when the ECS script attempts to deploy, there's nothing in the AWS container registry for us to deploy.
This specific commit resolved the issue.
It turns out that from what @pdxdiver found out, "login token expires after 12 hours".
So he researched the options and came up with this more durable solution.
Thanks Dan!
Problem
At the point of the
push.sh
script where it callsdocker login...
, this Travis build for the backend-service-pattern reports the following error:In the Raw Log further down from that request, we also see the log entry:
I'm also seeing the first error for the attempted deploy of the Budget backend.
Analysis
The second message may be unrelated to the first, but the first message is a definite error.
Question is, does this error mean that the subsequent
docker push
command doesn't succeed, and theecs-deploy.sh
script is re-using an old container image?Or is the "403 Forbidden" error a false negative, and the
docker push
is still succeeding (and we're deploying the updated container)?