Gem Building is Defunct
Gem building has been disabled since the move to Rackspace. This was because the system had to be rewritten to work with the new architecture and we had to provision…
Gem building has been disabled since the move to Rackspace. This was because the system had to be rewritten to work with the new architecture and we had to provision an entirely new VM for the sandboxed gem building – things we didn’t want holding up the move.
img http://img.skitch.com/20091008-1jbb3ywn14srhqjgiuxpsuf9w1.png http://gems.github.com
Well, it’s been a week and we’ve decided to not bring back the gem builder. It was a fun experiment but Jeweler and Gemcutter combined make it ridiculously simple to publish a gem. The gem builder use case (fork a project, make a change, publish a gem, install it) is now easier than ever using these tools.
As for namespace support, Gemcutter is working on it. We encourage you to help!
We will continue to serve old gems at http://gems.github.com/ for at least one year. Thanks.
Written by
Related posts
Q1 2025 Innovation Graph update: Bar chart races, data visualization on the rise, and key research
Discover the latest trends and insights on public software development activity on GitHub with the quarterly release of data for the Innovation Graph, updated through March 2025.
GitHub Availability Report: July 2025
In July, we experienced one incident that resulted in degraded performance across GitHub services.
Auf Wiedersehen, GitHub ♥️
tl;dr: I am stepping down as GitHub CEO to build my next adventure. GitHub is thriving and has a bright future ahead. The following is the internal post I sent to GitHub employees (Hubbers) this morning announcing my departure.