Interesting discovery as I work through Travis' S3 support.

You need to include the S3 authentication tokens in the .travis.yml file to upload files to S3, obviously.  Travis provides a way to store these tokens encrypted so they aren't in clear text in the .travis.yml file.  However (from the Travis docs):

Please note that secure env variables are not available for pull requests. This is done due to the security risk of exposing such information in submitted code. Everyone can submit a pull request and if an unencrypted variable is available there, it could be easily displayed.

Makes sense, and I doubt that there's a way around that.  It becomes a pretty annoying limitation for our needs, though.  It means we can't get the result images for a failed pull request test.


On 08/15/2013 01:03 PM, Michael Droettboom wrote:
Thanks to everyone who participated in the discussion today.

I didn't take great notes, but I thought I would synthesize the discussion into a list of action items on the wiki here:

If I forgot something, please add.  My memory gets fuzzier in my old age.


Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead. 
Download for free and get started troubleshooting in minutes.

Matplotlib-devel mailing list