At Travis CI, we also made some mistakes of where we focused our attention while building a product. Some things were more focused on building something that's technically sound rather than make sure we get a working product in front of customers quickly.
Early on, Travis CI started out as a test balloon if you will, with a few simple components to prove its technical viability as a continuous integration system. Leaving some challenges aside , we were able to scale it out quite …
I help run a little continuous integration service called Travis CI. For that purpose I built several home-baked things that help us collect metrics and trigger alerts.
I want to start with a little story. I spend quality time at coffee shops and I enjoy peeking over the shoulders of the guy who's roasting coffee beans. Next to the big roasting machine they commonly have a laptop with pretty graphs showing how the temperature in the roaster changes over time. On two occasions I found myself …
…Today is his first day at.
Besides having iOS code/design chops, he knows his way around active in open source , too. He's sharp, thoughtful, and has a knack for details that make an interaction special., , and . He's
Travis and I have already started working on an app together. We're excited to see where it goes.
Everyone, say hi to Travis.
Hopefully I've helped show that we're really just seeing the tip of the iceberg as far as optimizing JRuby using invokedynamic. More than anything we want you to report real-world use cases that could benefit from additional optimization, so we can target our work effectively. And as always, please try out your apps on JRuby, enable JRuby testing in Travis CI, and let us know what we can do to make your JRuby experience better!
…private projects, was a Josh Kalderimis of the Travis team had this to say about using JRuby on :beta tester.
We love JRuby, everything from the threading support to having the power of theat our finger tips. But what we love most is that we can set up a JRuby app in seconds, the same way as all of our other Heroku apps. push and it's live, no matter what the language.
We've been working with the JRuby team to make sure that the experience …
Edge Now on Ruby 2.0 with Travis CI
Little to read but Ruby 2.0 is now most clearly on the edge Rails developers' radar.
Deploying to with Git
Just last week,announced Ruby support for its AWS Elastic Beanstalk semi-automated deployment and scaling system. This tutorial by fills in all the blanks by walking us through using it from start to finish with a Rails…
Thank you to Travis CI for letting us know when our code is working (or broken) on various versions of Ruby.
Thank you to Rubygems.org for hosting software which makes our lives easier.
Thank you to Braintree for processing payments for ourselves and our clients.
Thank you to SendGrid for making world-class email delivery a no-brainer, and for your …
Various improvements to automated testing of integration with test libraries.
Make deprecation warnings more prominent.
Paul Revere is a library for "one off" announcements in .
appraisal had its ignored and got a check method which installs …evaluator
§ How to . Your Failed Test in Travis CI
§ GitHub Issues on the command line . Use your $EDITOR, not your browser.
§ From Client-side frameworks suck :
If you expect your framework to hold your hand through the battle field, you're going to end up hitting a mine at some point and if you don't understand or know how to write vanilla, you will never escape.
§ The art of saying with less: Using Writing Smells to . Your Email