-
Notifications
You must be signed in to change notification settings - Fork 366
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
Unable to deploy new gem with latest gems #574
Comments
Do you have a build log URL that shows the problem you are describing here? |
Hello @BanzaiMan, Yes, I do have a minimal example project and its failing logs - from 3rd-5th and 8th builds are failed due above problem, 9th succeeds when I removed and reinstalled both |
The problem lies somewhere else. In https://travis-ci.org/travis-ci/dpl/jobs/195179681#L1084, you see that our I don't know what the issue is exactly, though. |
One more observation: while I was desperately trying all possible combinations, one of my builds succeeded (note that this is another dummy project with similar name). Only two differences I see are that it has specific gem name as |
I appear to be having a similar problem: https://travis-ci.org/sepulworld/deadman-check/jobs/213292029 |
@chuwy Do you have a build that fails to deploy to rubygems.org with the |
Hi @BanzaiMan, yes I think this build was with |
Thanks for the pointer. The error is coming from here: https://github.com/rubygems/gems/blob/v1.0.0/lib/gems/client.rb#L27 The response from rubygems.org API was not valid JSON; instead, it was $ curl https://rubygems.org/api/v1/gems/eyeiqueryzdhfdawe.json
This rubygem could not be found. Once you have the gem registered, it should go fine. https://travis-ci.org/chuwy/iglaoo-test/builds/195116001#L288 I'm closing this. |
I am having the same issue even though my gem is registered and this same Travis deploy workflow was working before. Any ideas what could be wrong? travis.yml:
Logs:
|
Does the Ruby gem name match the name of the git repo? I had to explicitly
set the gem name in the . travis.yml because mine didn't match up. After I
did that it worked.
|
It does not match the repo name, but the gem name is specified in the gemspec. |
I just tried with the gem name in |
@emilienh Do you have a build log URL that shows the problem you are describing? |
Here it is: https://travis-ci.org/Smartling/api-sdk-ruby/jobs/234068772 |
Please try moving the gem name under the 'deploy:' hash in .travis.yml Like: https://github.com/sepulworld/deadman-check/blob/master/.travis.yml#L12 |
That did it, thanks a lot! |
I submitted a PR to add one additional log line that I believe would help prevent confusion when a build fails with this error. #633 |
Due to an issue[1] with Travis' gem publishing, it's been necessary to manually publish the initial version of this gem. This is a test to ensure that Travis can now properly publish. Once this is confirmed, we'll release a non-prerelease version following the process in the README. [1]travis-ci/dpl#574
I think this issue should not have been closed without being fixed or updating the documentation about it. It's weird that to ask people to upload their new gem manually before to use travis' deploy rubygems function. It's so confusing. |
Having pretty standard configuration:
I couldn't push new gem to RubyGems.org. Travis gave me following error:
Seems that problem is in updated
dpl
>= 1.8.30
which transitively includesgems-1.0.0
.When I used this deployment script, my problem was solved:
The text was updated successfully, but these errors were encountered: