-
Notifications
You must be signed in to change notification settings - Fork 649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Publish gem on release #223
Comments
Can't u commit the API key file? |
committing the API key means anyone can replace the gem. better to add it to teamcity as an encrypted property |
Not sure it can be passed to the publish method as a parameter :( think it only works with a file in user profile.. Dumb Sent from my Windows Phone From: Simon Croppmailto:notifications@github.com committing the API key means anyone can replace the gem. better to add it to teamcity as an encrypted property — |
According to the doco:
So doesn't this mean that we actually need to install gem on the build server + install the certificate in the store (http://guides.rubygems.org/command-reference/#gem-cert) |
Here is the other option: |
Please update the gem to 1.3.3! |
@JakeGinnivan did we get anywhere with this one? I have never played with gem's, so don't know where to start, but was thinking couldn't we add the build step to take the encrypted variable from TeamCity, write it to a file in the right place, and then tidy up afterwards? A bit of a cludge, but just a thought. |
Owners are particular and @danielmarbach - so yeah, they need to get an API key and put in as a password parameter in teamcity. Then we can just |
Bump, can someone make this happen? |
@johnsimons looks like the only way to make this work is to have an API key in a file, would you be able to set this up?
http://guides.rubygems.org/command-reference/#gem-push
The text was updated successfully, but these errors were encountered: