[DEPRECATED] Upload artifacts after running your tests to S3 (Unmaintained. See https://github.com/travis-ci/artifacts)
Ruby
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
bin Extend to accept clone parameter (without tests) Aug 12, 2013
lib/travis fix #29 May 20, 2014
script
spec Fix typo Aug 18, 2013
.gitignore Extend to accept clone parameter (without tests) Aug 12, 2013
.rspec Minimal working version Nov 15, 2012
.travis.yml
Gemfile Updating Gemfile to use the https rubygems source May 9, 2013
README.md Add note about travis-ci/artifacts Jan 9, 2015
travis-artifacts.gemspec Bump version to 0.3.0 May 5, 2014

README.md

Travis Artifacts

🚫 This project is no longer maintained. Please see https://github.com/travis-ci/artifacts 🚫

If your tests produce files, for example stack traces or logs, you can easily upload them to Amazon S3.

See the Travis blog for more:

http://about.travis-ci.org/blog/2012-12-18-travis-artifacts/

The minimum AWS policy needed for the gem to work

{
  "Statement": [
    {
      "Action": [
        "s3:ListBucket"
      ],
      "Effect": "Allow",
      "Resource": [
        "arn:aws:s3:::your-bucket"
      ]
    },
    {
      "Action": [
        "s3:PutObject",
        "s3:PutObjectAcl"
      ],
      "Effect": "Allow",
      "Resource": [
        "arn:aws:s3:::your-bucket/*"
      ]
    }
  ]
}