Josh is making his way around the globe
from New Zealand to Berlin by way of Amazon re:Invent, and
Hiro is on his way back from
RubyConf. As luck would have it, the stars aligned so that they
can both visit Pittsburgh! The reason for this, of course, is to
indulge in a healthy dose of tunnels and bridges. We'll also be
doing a bit of Travis fun in the time remaining.
This coming Friday, November 21st 2014, we'll be hanging out at
Marty's Market in the Strip, one of
our favorite coworking spots, from 9:30am until 1pm.
From time to time we get requests from you wonderful Travis CI users for brand assets to use. Sometimes you are talking about how you use Travis CI at a conference and want our mascot. Sometimes you just want to show love on your site that you test on Travis CI. There are a couple times you’re just asking when it’s appropriate to use our logo and when it’s not. Well, to save you some extra time (because we know you design your slides at the last possible second) we’ve added a Logo and Brand Usage page to our site!
Actually, this page is a long time coming. Since I started at Travis CI last September I’ve not only made changes to the UI, which you’ve probably noticed, but I’ve also redefined some parts of our brand language. You probably won’t need to know that we use Source Sans Pro as our typeface or that our shade of mustache red is PMS 7599 C but we thought we’d throw that in there just in case you were curious.
All this was just for you! But please have a quick read on our brand Do’s and Don’ts! For example: please DO bake me some vegan cookies in the shape of the mascot! Totally worth the tax to ship to Germany! And please DON’T use the logo in artwork for profit.
If you have any further questions, or have something you’d like to see on that page that isn’t currently available, feel free to holler at us firstname.lastname@example.org!
If you are deploying to Heroku from Travis CI, you might have seen a warning pop up in your build logs lately: We are changing the default strategy from "anvil" to "api".
But what does this mean? Up until recently, Travis CI could deploy to Heroku by two different means: Anvil and Git. We call these "strategies" and you can switch between them by setting the strategy option in your deploy section. Both strategies have their issues.
The Git strategy does what you would do locally: git push your application to Heroku. It would generate a new SSH key for your Heroku account on every single deploy (and subsequently remove it again). This would trigger a new email, potentially for all builds on Travis CI.
On the other hand, the anvil strategy uses an unofficial build server, which accepts archives of the application you want to deploy. All it needs is API access (via a token or username/password). However, it comes with a few dependencies, which makes it slower than the git strategy. But worst of all, it is deperecated and will be shut down in the near future.
Lucky for us, the awesome folks at Heroku have been busy finding a solution for this. And they didn't just come up with one, but two approaches
The Build API
Heroku launched their Build API a while ago. We have had support for it since October 2nd, but users had to manually set the strategy to "api" in their .travis.yml.
Starting on Monday, November 17, this will be the new default strategy. Internally, all Travis CI will be doing, is bundle up the current project directory as a tarball and upload it to the Heroku API. It will then stream the buildpack compilation logs back from the Heroku API to the Travis CI web interface.
In theory, the only change this will cause from an end user's perspective are faster deployments.
More recently, Heroku has made it possible to do a git push over HTTPS. This eliminates the need to generate an ssh key to be able to deploy via git. We have an implementation ready, and it will replace our current "git" strategy, also on Monday.
Reverting to SSH or Anvil
If these changes will somehow break your deployments, you can set the strategy option in the deploy section of your .travis.yml to "anvil" or "git-ssh" respectively.
However, most importantly, you should get in touch. Both the git-ssh and the anvil strategy will be discontinued in the near future.
A strategy for the future
Ideally, with this update, you as our user should never have to worry again about the different options we might have for deploying to Heroku. Things should just work™. We will monitor this change in the coming weeks and gather user feedback. If it is all to our pleasing, we might remove the strategy option entirely in the future.