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
Your stack, your rules: Introducing custom agents in GitHub Copilot for observability, IaC, and security
Use partner-built Copilot agents to debug, secure, and automate engineering workflows across your terminal, editor, and github.com.
The ultimate gift guide for the developer in your life
Finding the perfect gift for your favorite developer is easy with our top tips.
Why developers still flock to Python: Guido van Rossum on readability, AI, and the future of programming
Discover how Python changed developer culture—and see why it keeps evolving.