Ruby gems and “Couldn’t get release_id, upload failed?”
I've been experimenting with Ruby gems over the past few weeks. I use a couple of other gems to make the process easier including rubyforge, jeweler and newgem.
Jeweler has a rake task 'rubyforge:release' that uploads your gem for you. The problem was that it would timeout and give me "Couldn't get release_id, upload failed?". I assumed that I had configured something wrong so I tried to upload the file directly to rubyforge. That didn't work either so I assumed (wrongly) that my project had something wrong with it. I was about to give up when I decided to check my gem size. It was 100MB!
Somehow I was packaging the gem inside itself on each release and it had grown into a beast. So if your release is timing out check your gem size and make sure it isn't going nuts.
More from jbasdf
- How New Carpet and Rattlesnake turned me into a Consultant or What the Hell Happened?
- Rails Conf Intro from Chad Fowler and Some Stuff from the Mountain West Ruby Conference
- A copy of ApplicationController has been removed from the module tree but is still active! And can’t dup NilClass
- Mac OSX and the Samsung ML1740 on a network
- First Time on the new Santa Cruz Blur XC, and Near Death Experiences
![Recommend [jbasdf]](http://s3.amazonaws.com/arkayne-media/img/logo-recommend-me.png){kind=logo}
-
grosser
Justin Ball is a software consultant and entrepreneur with a passion for Ruby. He evolved from a C++ and .Net monkey into a python programmer and finally found Ruby. In the rare moments when he isn't writing code, talking about code or measuring his code productivity in profanity per hour, you can find him on his bike in the mountains or on the roads surrounding Cache Valley. 
