Skip to content
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

Closed
JakeGinnivan opened this issue Jul 17, 2014 · 9 comments
Closed

Publish gem on release #223

JakeGinnivan opened this issue Jul 17, 2014 · 9 comments
Assignees

Comments

@JakeGinnivan
Copy link
Contributor

@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

@johnsimons
Copy link

Can't u commit the API key file?

@SimonCropp
Copy link
Contributor

committing the API key means anyone can replace the gem. better to add it to teamcity as an encrypted property

@JakeGinnivan
Copy link
Contributor Author

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
Sent: ý7/ý17/ý2014 8:13 AM
To: Particular/GitVersionmailto:GitVersion@noreply.github.com
Cc: Jake Ginnivanmailto:jake@ginnivan.net
Subject: Re: [GitVersion] Publish gem on release (#223)

committing the API key means anyone can replace the gem. better to add it to teamcity as an encrypted property


Reply to this email directly or view it on GitHubhttps://github.com//issues/223#issuecomment-49266521.

@johnsimons
Copy link

According to the doco:

-k, -​-key KEYNAME - Use the given API key from ~/.gem/credentials

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)

@johnsimons
Copy link

Here is the other option:
http://stackoverflow.com/a/3429408/90882

@agross
Copy link
Contributor

agross commented Nov 4, 2014

Please update the gem to 1.3.3!

@gep13
Copy link
Member

gep13 commented Jan 6, 2015

@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.

@JakeGinnivan
Copy link
Contributor Author

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 gem push. Instructions at http://guides.rubygems.org/publishing/#publishing-to-rubygemsorg

@JakeGinnivan
Copy link
Contributor Author

Bump, can someone make this happen?

@JakeGinnivan JakeGinnivan self-assigned this Jul 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants