Following in the wake of PyPI and NPM support, we’re happy to announce support for deploying to AppFog and Amazon S3!

Deploying to AppFog

Getting started is easy. Sign up for an account with AppFog, and create an app.

Once your app is set up, simply add the following to your .travis.yml:

deploy:
  provider: appfog
  email: "YOUR EMAIL"
  password: "YOUR PASSWORD" # should be encrypted

To encrypt your password, install the Travis client, then run travis encrypt. You will be prompted to enter in your password.

Or, assuming you have the Travis client installed, just use the setup command:

$ travis setup appfog

Pushing to S3

To set up pushing to S3, you’ll first need to create an account with Amazon S3, and create a bucket.

Once your bucket is set up, just add this to your .travis.yml:

deploy:
  provider: s3
  access-key-id: "Your ACCESS KEY ID"
  secret-access-key: "YOUR SECRET ACCESS KEY" # should be encrypted
  bucket: "YOUR S3 BUCKET NAME"

As with AppFog, you’ll need to install our command line client in order to encrypt the secret access key.

Alternatively, you can just use the setup command:

$ travis setup s3

That’s it!

Is your provider still missing?

We’ve been adding support for lots of new providers, but there are still plenty more out there. If you’d like to support for your cloud provider on Travis CI, please shoot us an email.

Or, send us a pull request over at our dpl repository.

Today we’re launching the Travis Foundation, an initiative to improve and foster Open Source!

Non-profit support for Open Source

Travis Foundation is an institution aiming to foster the Open Source community: We’ll help fund hand-picked projects, work towards more diversity and support amazing initiatives!

We want it to become an institution that promotes and encourages changes in the community, connects people and ideas.

Travis CI has always been very much rooted in Open Source. Working with the community to build a service for the community has been one wild love and success story. Since Travis CI now is an established, solid service, it is time to give back even more.

Our first project

After coordinating and managing Rails Girls Summer of Code - which was our unofficial first project we took on - we are now focusing on organizing Open Source Grants. This means we help set up funding for hand-picked Open Source projects. Either if it’s a new project or an established one that needs help being continued - we want to support progress and amazing ideas!

The first project we took on for our Open Source Grants is RVM. We are happy to announce that we’ve secured funding for RVM for the next two months! This means that the current Maintainer Michal Papis can work fulltime on bootstrapping RVM 2.0 until mid January. This is made possible by the great people of

who are supporting and sponsoring this project, which we are truly grateful for! The journey will start today and we are looking forward to see this wonderful project start off.

How you can get involved

Travis Foundation is a non-profit initiative that wants to help make our community an even better place. Since we have lots of ideas and even bigger plans, we are always looking for people to help us on that journey. So if you want to get on board please get in touch, we’d love to hear from you.

Thanks again to PAYMILL for being our launch partner and supporting us and our mission from the first minute. There are some really great things ahead and it’s time to raise our glasses (or tea pots/ coffee mugs/ Club-Mate bottles for that matter):

To the Travis Foundation and a great journey ahead!

Cheers!

Visit the Travis Foundation site and read on about our goals, projects, and how to contribute.

Build emails are our most important means of communicating with our users. For the longest time, these notifications have been very straight to the point and in your face, especially when a build fails.

They’ve been lacking a bit more context as well to figure out what went wrong and who pushed the commit.

We’re sending up to 14.000 of these emails per day, so we wanted to improve their overall appearance and usefulness. The latter is still a work in progress, but we’re moving in the right direction.

Thanks to Jessica Allen, we made a big step towards improving our communication on broken builds.

As you’ve probably noticed, we pushed these out a few weeks ago, but we still would like to take the opportunity to talk about them and to thank Jessica for her awesome work!

Here’s how our build emails look now:

We included the Avatar that’s configured on GitHub, and condensed the amount of information shown overall. The red is dialed down to not scream at you when you open the email.

Same for the green build emails. Let’s face it, everyone loves getting these, but we made the red more subtle too:

We have a lot of ideas on how to improve the emails in the future, and how to make them more useful to get better insight about what’s been broken, stay tuned!

Thank you, Jessica!