how many fs can you find in:
q: travisci not uploading files created with grunt below is my .travis.yml, im using grunt to compile my sass, and minimize js and images which seem to work fine, however none of those files get deployed to elastic beanstalk.  i added skip_cleanup: true which according to the docs should fix this issue but to no avail.
language: php

before_install:
  - nvm install 0.10.38
  - npm set progress=false
  - npm install -g grunt-cli grunt grunt-bower -loglevel=error
  - gem install dpl

script:
  - echo success

before_deploy:
  - cd ${travis_build_dir}/wp-content/themes/myapp && npm install --loglevel=error
  - cd ${travis_build_dir}/wp-content/themes/myapp && grunt build
  - cd ${travis_build_dir}
  - ls ${travis_build_dir}/wp-content/themes/myapp

env:
  - elastic_beanstalk_label=$travis_commit

deploy:
  skip_cleanup: true
  provider: elasticbeanstalk
  region: us-east-1
  app: app
  env: app-staging
  bucket-name: elasticbeanstalk-us-east-1-aaaaaaaa123
  access_key_id: ${staging_aws_access_key_id}
  secret_access_key: ${staging_aws_secret_key}  
  on:
    branch: staging


a: i never did find an answer to this using only travis to build and ship, i had to manually create a zip file after travis ran grunt build and use awscli to upload it to s3 and trigger an eb deployment.  
.travis.yml

language: node_js
node_js:
  - 0.10

before_install:
  - sudo pip install awscli
  - ls /usr/local/bin/
  - which aws
  - npm set progress=false
  - npm install -g grunt-cli grunt grunt-bower -loglevel=error

script:
  - echo success

before_deploy:
  - cd ${travis_build_dir}/wp-content/themes/mytheme && npm install --loglevel=error
  - cd ${travis_build_dir}/wp-content/themes/mytheme && grunt build
  - cd ${travis_build_dir}
  - echo $(git rev-parse --short head) >> /tmp/version
  - cd ${travis_build_dir} && zip -0 /tmp/travisci-$(cat /tmp/version).zip -r ./ -x wp-content/themes/mytheme/node_modules/* *.git* > /dev/null 
  - chmod +x scripts/deploy/production.sh

deploy:
  - provider: script
    skip_cleanup: true
    script: scripts/deploy/production.sh
    on:
      branch: master

scripts/deploy/production.sh
mkdir ~/.aws
touch ~/.aws/config
chmod 600 ~/.aws/config
echo [default] > ~/.aws/config
echo aws_access_key_id = $aws_access_key_id >> ~/.aws/config
echo aws_secret_access_key = $aws_secret_access_key >> ~/.aws/config
cp ~/.aws/config ~/.aws/credentials
aws s3 cp /tmp/travisci-*.zip s3://elasticbeanstalk-us-east-1-1234567890/
aws elasticbeanstalk create-application-version --region us-east-1 --application-name app --version-label `cat /tmp/version` --source-bundle s3bucket=elasticbeanstalk-us-east-1-1234567890,s3key=travisci-`cat /tmp/version`.zip
aws elasticbeanstalk update-environment --region us-east-1 --environment-name app-production --version-label `cat /tmp/version`


a: i think its because the deploy tool uses git ls-files to select the files for deployment. to work around you can either use git add -f ignored_folder before deploy or try to modify .gitignore on the fly.

user
There are 29 "f"s.
assistant