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

npm deploy issue #4738

Closed
gyzerok opened this Issue Sep 2, 2015 · 15 comments

Comments

Projects
None yet
3 participants
@gyzerok
Copy link

gyzerok commented Sep 2, 2015

After moving my npm publish process to travis I've ended up with npm install problems. To reproduce error you can just do npm i adrenaline@0.4.0. For the old versions which I've published with my own all is ok npm i adrenaline@0.2.0.

@gyzerok gyzerok changed the title Shasum check failed npm deploy issue Sep 2, 2015

@BanzaiMan

This comment has been minimized.

Copy link
Member

BanzaiMan commented Sep 2, 2015

Could you point to the failed deployment?

@BanzaiMan BanzaiMan added the deployment label Sep 2, 2015

@gyzerok

This comment has been minimized.

Copy link
Author

gyzerok commented Sep 2, 2015

@BanzaiMan You can check deploy for this build.

@BanzaiMan

This comment has been minimized.

Copy link
Member

BanzaiMan commented Sep 2, 2015

You are deploying from all branches, so the first job in the build matrix to finish will upload to npm (https://travis-ci.org/gyzerok/adrenaline/jobs/78018303#L590), and the subsequent ones (https://travis-ci.org/gyzerok/adrenaline/jobs/78018299#L589 https://travis-ci.org/gyzerok/adrenaline/jobs/78018301#L590) fail.

You should restrict your deployment to exactly one job (http://docs.travis-ci.com/user/deployment/#Conditional-Releases-with-on%3A) to avoid errors. (If you don't care about which branch uploads, and can ignore the errors, you don't have to do this.)

@BanzaiMan BanzaiMan closed this Sep 2, 2015

@BanzaiMan BanzaiMan reopened this Sep 2, 2015

@BanzaiMan

This comment has been minimized.

Copy link
Member

BanzaiMan commented Sep 2, 2015

I don't know what is causing the checksum error, though. Did npm upload a faulty package? Or does subsequent uploads mangle the checksum, even thought they failed?

@gyzerok

This comment has been minimized.

Copy link
Author

gyzerok commented Sep 2, 2015

@BanzaiMan I would try to change multiple deploy branch to a single branch. Hope it would help. Let me come tomorrow with the results.

Thank you for helping!

@BanzaiMan

This comment has been minimized.

Copy link
Member

BanzaiMan commented Sep 2, 2015

If deploying from a single branch helps (which I believe will), it seems to me that there is something wrong with the way npmjs.org handles multiple upload attempts.

@gyzerok

This comment has been minimized.

Copy link
Author

gyzerok commented Sep 3, 2015

@BanzaiMan Issue solved with one-branch deploy. It would be nice to mention it in the docs.

@BanzaiMan

This comment has been minimized.

Copy link
Member

BanzaiMan commented Sep 4, 2015

What should be documented?

@gyzerok

This comment has been minimized.

Copy link
Author

gyzerok commented Sep 8, 2015

@BanzaiMan this case I guess. How anyone else should get this?

@BanzaiMan

This comment has been minimized.

Copy link
Member

BanzaiMan commented Sep 8, 2015

Conditional release is already documented. It is not clear to me how the checksum got corrupted; is it possible that a second upload attempt did? Have you contacted npmjs.org support?

@kbrock

This comment has been minimized.

Copy link

kbrock commented Oct 5, 2015

It seems that the problem is on npm's side.

Does anyone have a fix? I did find npm/npm#9574 (comment)

@BanzaiMan

This comment has been minimized.

Copy link
Member

BanzaiMan commented Nov 24, 2015

Is there anything to do on our end?

@kbrock

This comment has been minimized.

Copy link

kbrock commented Nov 24, 2015

@BanzaiMan I am not sure. Think this may have to do with npm's infrastructure and bad proxy servers. So it would seem to be a non-travis issue. But it is happening way too often to just say "not travis".

@BanzaiMan

This comment has been minimized.

Copy link
Member

BanzaiMan commented Dec 18, 2015

I've documented this with travis-ci/docs-travis-ci-com@ffed550. We are happy to look into this issue if the deployment from a single job continues to cause problems. In the meantime, I'm closing this.

@BanzaiMan BanzaiMan closed this Dec 18, 2015

@kbrock

This comment has been minimized.

Copy link

kbrock commented Dec 18, 2015

@BanzaiMan thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.