Build failing in travis: "No stash entries found" and "missing access_key_id"

Deployment
1

Hi Team,

Im trying to build and deploy to the AWS elasticbeakstalk its getting failing throwing the below error. can you someone please help me on this

Installing deploy dependencies
dpl.2
356Preparing deploy
358No stash entries found.
359missing access_key_id
360failed to deploy.

Travis.yml file.

sudo: required
language: generic

services:
  - docker

before_install:
  - docker build -t dkmaruthi/docker-react -f Dockerfile.dev .

script:
  - docker run -e CI=true dkmaruthi/docker-react npm run test

deploy:
  provider: elasticbeanstalk
  region: 'ap-south-1'
  app: 'docker'
  env: 'docker-env'
  bucket_name: 'elasticbeanstalk-ap-south-1-275166638116'
  bucket_path: 'docker'
  on:
    branch: master

    
    acces_key_id: $AWS_ACCESS_KEY
    secure_key_id: "$AWS_SECRET_KEY"
2
3

Getting same error again

4

Hi @dkmaruthi this is a solution. indentation mistake

deploy:
  provider: elasticbeanstalk
  region: 'ap-south-1'
  app: 'docker'
  env: 'docker-env'
  bucket_name: 'elasticbeanstalk-ap-south-1-275166638116'
  bucket_path: 'docker'
  on:
    branch: master
  acces_key_id: $AWS_ACCESS_KEY
  secure_key_id: "$AWS_SECRET_KEY"
5

Based on the Travis update, you need to modify a few lines of code, Alse need to add “skip_cleanup: true” under deploy:
Because Travis CI now consider default variable as secure.

deploy:
  provider: elasticbeanstalk
  edge: true
  region: 'ap-south-1'
  app: 'docker'
  env: 'docker-env'
  bucket_name: 'elasticbeanstalk-ap-south-1-275166638116'
  bucket_path: 'docker'
  on:
    branch: master
  access_key_id: $AWS_ACCESS_KEY
  secure_key_id: "$AWS_SECRET_KEY"
  skip_cleanup: true

This worked for me.

6

Is this something coincidental or it is a must that the few additional lines of code must be applied in order for Travis to build the app ?

7

I actually did what you suggested and i get the following in the Travis console

$ rvm $(travis_internal_ruby) --fuzzy do ruby -S gem uninstall -aIx dpl

272Unknown option: --secrect_access_key you mean? secret-access-key

273failed to deploy

From that I would assume that the issue would be to the actual build engine due to recent updates, because I have following a course and the line of codes is word for word