Travis-CI Docker Image Build and Push to AWS ECR

.travis.yml

sudo: required #is required to use docker service in travis

language: php #can be any language, just php for example

services:
  - docker # required, but travis uses older version of docker :(

install:
  - echo "install nothing!" # put your normal pre-testing installs here

script:
  - echo "no tests!" # put your normal testing scripts here

after_success:
  - docker --version  # document the version travis is using
  - pip install --user awscli # install aws cli w/o sudo
  - export PATH=$PATH:$HOME/.local/bin # put aws in the path
  - eval $(aws ecr get-login --region us-east-1) #needs AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY envvars
  - docker build -t my_example_app .
  - docker tag my_example_app:latest [your_ecr_account].dkr.ecr.us-east-1.amazonaws.com/my_example_app:latest
  - docker push [your_ecr_account].dkr.ecr.us-east-1.amazonaws.com/my_example_app:latest
  
# sadly, travis doesn't cache docker builds yet, so each build will take a while

@matheusmessora your env setings is wrong, the correct is

env:
     - APP_NAME=my_example_app AWS_ECR_ACCOUNT=09500000

I referenced this: https://docs.travis-ci.com/user/environment-variables/#defining-multiple-variables-per-item

@matheusmessora do you find tagging with the build number more valuable than the git commit hash or PR title?

For those interested here's the list of Travis-provided env vars possibly suitable for tagging images:
https://docs.travis-ci.com/user/environment-variables/#convenience-variables

Old thread for me. But the build is incremental. That helped a lot in some troubleshooting.

But nice link, I'll give a try