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
GitHub availability report: March 2026
In March, we experienced four incidents that resulted in degraded performance across GitHub services.
GitHub Universe is back: We want you to take the stage
Get inspired by five of the most memorable, magical, and quirky Universe sessions to date.
What’s coming to our GitHub Actions 2026 security roadmap
A look at GitHub Actions’ 2026 roadmap, outlining how secure defaults, policy controls, and CI/CD observability harden the software supply chain end to end.