You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My deployment (running ecs-deploy via CodeBuild) has started failing since last week with exit status code 255 (no explicit change from me; I do get the latest master version of ecs-deploy on each build though). There is no error message. It deploys fine if I run the same command (using the same image etc.) locally.
I looked at the script and couldn't find anywhere where the exit status code can be 255. If someone can point me to a direction where I can look in order to debug this issue it will be very helpful.
The text was updated successfully, but these errors were encountered:
I discovered that aws ecs commands are failing because of a version conflict between the boto libraries (boto3 and botocore) installed by awscli and the ones which were being installed by the application's test runner for running unit tests.
I upgraded the boto3 package in the application's requirements file.
This removed the version conflict and the aws ecs command and hence, ecs-deploy was able to run successfully again.
It might be good to have a "--debug" flag to ecs-deploy which returns the debug output of a failed awscli command.
Hello
My deployment (running ecs-deploy via CodeBuild) has started failing since last week with exit status code 255 (no explicit change from me; I do get the latest master version of ecs-deploy on each build though). There is no error message. It deploys fine if I run the same command (using the same image etc.) locally.
I looked at the script and couldn't find anywhere where the exit status code can be 255. If someone can point me to a direction where I can look in order to debug this issue it will be very helpful.
The text was updated successfully, but these errors were encountered: