Capistrano: show current deployed revision

Capistrano task to show currently deployed revision

Automated Pull Request Review Comments

We are excited to announce a new way to integrate Code Climate with GitHub pull requests. In addition to our existing pull request statuses and browser extension, there are two new ways to bring Code Climate results into your pull requests: sum…

Read more at the source

Quick tip: AWS S3 invalid certificate

If you are getting invalid SSL certificate error in the browser when serving assets from the s3 bucket and using s3 bucket name as a subdomain. This quick tip might be a help.

In my case, I had a dot in the bucket name so the domain created was like https://akhil.bansal.s3.amazo…… I removed the dot from the bucket name and it worked perfectly. Looks like S3 ssl certificate does not support a dot in the subdomain.

Read more at the source

SwiftLint Plugin for Code Climate

We recently launched Swift as our 8th officially supported language on Code Climate, and now we’re excited to introduce our SwiftLint plugin to complement our native support. SwiftLint is a tool to enforce Swift style and conventions, loos…

Read more at the source

Default Threshold Adjustment for Go Maintainability Checks

In response to feedback from our Go community, we’ve increased the default threshold for the following Go maintainability checks to reflect the language’s convention and to eliminate false positives:

File lines
Method lines
Method complexity

As a result, you might see a one-time, unexpected improvement on the maintainability ratings for your Go repositories. The subsequent analysis should be stabilized after this one-time adjustment.

If you have questions about how our configurations work, please check out our documentation here.

Read more at the source

Swift has arrived!

Swift tweet

We’re thrilled to announce that Swift is the 8th officially supported language on Code Climate!

Just like our other supported languages (Go, TypeScript, JavaScript, PHP, Python, Java, Ruby), we now provide our out-of-box 10-point technical debt assessment, and full support for tracking test coverage of Swift applications. Additionally, we’ve upgraded our Tailor plugin to the latest version.

Please add a Swift repo on your Code Climate account and give it a try! We would love to hear what you think.

Read more at the source

Launching Today: Velocity

Data-driven insights to boost your engineering capacity

Today we’re sharing something big: Velocity by Code Climate, our first new product since 2011, is launching in open beta.

Velocity helps organizations increase their engineering capacity by identifying bottlenecks, improving day-to-day developer experience, and coaching teams with data-driven insights, not just anecdotes.

Velocity helps you answer questions like:

Which pull requests are high risk and why? (Find out right away, not days later.)
How does my team’s KPIs compare to industry averages? Where’s our biggest opportunity to improve?
Are our engineering process changes making a difference? (Looking at both quantity and quality of output.)
Where do our developers get held up? Do they spend more time waiting on code review or CI results?

Learn more about Velocity

Why launch a new product?

Velocity goes hand-in-hand with our code quality product to help us deliver on our ultimate mission: Superpowers for Engineering Teams. One of our early users noted:

“With Velocity, I’m able to take engineering conversations that previously hinged on gut feel and enrich them with concrete and quantifiable evidence. Now, when decisions are made, we can track their impact on the team based on agreed upon metrics.” – Andrew Fader, VP Engineering, Publicis

Get started today

We’d love to help you level up your engineering organization. Request a free trial and we’ll be in touch right away. As a special thank you for our early supporters, anyone who begins a free, 14-day trial before Friday, February 16th will get 20% off their first year.

Read more at the source

To Serve Man, with Software

I didn’t choose to be a programmer. Somehow, it seemed, the computers chose me. For a long time, that was fine, that was enough; that was all I needed. But along the way I never felt that being a programmer was this unambiguously great-for-everyone career field with zero downsides. There

Read more at the source

New: Golang is here!

We’re thrilled to announce that Go is the 7th officially supported language on Code Climate!

Just like our other supported languages (Typescript, Javascript, PhP, Python, Java and Ruby), we now provide our out-of-box 10-point technical debt assessment , and full support for tracking test coverage of Go applications. Additionally, we’ve promoted 3 Go plugins – gofmt, golint, and govet out of beta, and our team will support and keep them updated going forward.

Please add a Go repo on your Code Climate account and give it a try! We would love to hear what you think.

Read more at the source

Filter issues by source and language

Our Issues page now supports filtering by source (ex. a particular plugin) and language.

We hope this helps you divide and conquer your project’s issues with greater ease. Please let us know what you think!

Read more at the source

cap::deploy::rollback

June 6, 2013

This is a post which we wrote for internal use at TaskRabbit. It is very specific to our infastructure and topology, however we wanted to share it in the hopes that it might provide value to you as well.

When you Move Fast and Break Things, often times… you sometimes end up breaking things.

A good engineer understands the ecosystem her application runs within, and how to check for and fix deployment errors. Perhpas your most recent deployment added a new gem that ended up consuming far more ram than you expected, or something went wrong with your asset pipeline and now there is no CSS. This post is a survey of some of the tools we use at TaskRabbit to deploy and rollback.

Capistrano

TaskRabbit uses capistrano to deploy all of our applications. We have even modified Capistrano so we can use it universally to deploy Rails, Sinatra, and even node.js applications. This allows all of our developers to know the patern each deploy will follow, and we can ensure that there will be no supprises between applications. Below you can see what each capistrano does (with our extensions).

At it’s simplest case, capistrano creates a timestamped ‘release’ directory every time you deploy which is eventually symlinked to the ‘current’ directory. Each deploy you:

Create a new deploy directoy
Update code (git pull)
Run precompile (assets, etc)
Run database update (migrations, seeds)
Change the symlink (this is what capistrano called “commit”)
Restart the web workers (unicorns)
Clear the cache
Restart the background workers (resque)

98% of the time, our deployments work without any problems. 1% of the time something goes wrong, and we can recover with cap deploy:rollback. This built-in capistano command reverts back to the previous release, redoes the symlink, and restarts the workers. It is very simple and very effective. You can do it manually if you need to. The final 1% of the time we need to resort to the tools lower in the stack.

Monit

TaskRabbit uses monit to control all of our application stack, including nginx, unicorn, and resque. This allows us to have a simple control interface (IE: monit start unicorn) for all the applications we care about. While these applications may have complex boot arguments, a human can easily control them. This makes contolling the system in an emergency simple. If something goes wrong with monit, we can still inspecct the monit.rc boot files to know what we need to run manually. Monit also provides a nice aggrigate reporting tool, m/monit so we can report on and check all of our serer’s status.

Chef

We use chef to configure our servers. To us, this means not only the underlying packages and apps, but also all of the configuration files we need. This includes various .yml files most rails apps need along with ruby itself. If something is wrong with your application, it might be worth it to manually run chef-client

OS

We use a combination of Ubuntu and Joyent’s SmartOS operating system. It’s important to know how to read load average spikes, tell which processes are running, and how to peek into the system’s recourse. Are you out of ram or disk space? How can you recover it?

External Services

Did this deploy change an API endpoint or expect a differenent schema from another aplication? It’s improtant to have higher level metrics about the interplay between your apps. Is your resque queue backed up, or are new users not getting sent emails?

Deployment Test

At TaskRabbit, we don’t do continious deployment, but we do want to reduce the time it takes to get a feature up on production as much as possible. To this end, we allow any team lead to deploy as long they demonstrate that they can recover from a bad deployment. In the image below, you will see the questions on our deployment test. Can you answer them all?

[…]

The Ruby Rails Aggregator

Data-driven insights to boost your engineering capacity

Why launch a new product?

Get started today