Integrate your CI server with Pivotal Tracker and Code Climate

From day one, all our clients are allocated a staging server for their project, so they can review the work done on a daily basis.
We use Pivotal Tracker and Basecamp to communicate the progress, Github for our code, Codeship for continuous integration and continuous deployment, HipChat for our internal communication, and finally CodeClimate to ensure our code quality.

Why did we choose CodeShip?

These days there are plenty of continuous integration services.

We first started to maintain our own Jenkins server, but quickly realised that it was a waste of our time. So we quickly moved to Codeship.

Codeship meets Pivotal Tracker

Codeship is dead easy to use.

You define your project on their interface, then enter some per branch deployment recipes and off you go. Now every time you git push some code, it will pass the tests and deploy the code to your server when it’s green.

But that means we would have to go back to Pivotal Tracker and update our cards status once Codeship has deployed it.

What we were looking for was marking our cards as deployed automatically when Codeship deploy them.

What did it change?

Knowing that your push will finish a certain card, and that this card is tagged in your source control, makes this very easy to go back to if a bug occurs.
The continuous integration / deployment, is one of those things that I will never look back on!
You should never be afraid to deploy. And knowing that every push (to certain branches) will perform this deploy forces to write a deployable code straight away.

The one I’m still unsure about is Code Climate. Don’t get me wrong this tool looks really good. But I’m wondering if our codebase is not too small to really justify the cost of a tool like this.

Peace of mind – we are sure not to push half-baked features, or that a lazy dev won’t pass the suite.Easy deployment – in fact it looks like we never deploy really as it’s Codeship responsibility.