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

Travis npm deploy failed #773

Closed
stephenplusplus opened this issue Jul 31, 2015 · 12 comments · Fixed by #957
Closed

Travis npm deploy failed #773

stephenplusplus opened this issue Jul 31, 2015 · 12 comments · Fixed by #957
Assignees

Comments

@stephenplusplus
Copy link
Contributor

@jgeewax

https://travis-ci.org/GoogleCloudPlatform/gcloud-node/builds/73223799#L2964-L2966

Looks like we need to do something different with regards to the api_key in our .travis.yml. Here's a guide http://docs.travis-ci.com/user/deployment/npm/

@jgeewax
Copy link
Contributor

jgeewax commented Jul 31, 2015

Any links you can send over ?

@stephenplusplus
Copy link
Contributor Author

Sorry, I prematurely submitted the issue. Refresh :)

@jgeewax
Copy link
Contributor

jgeewax commented Jul 31, 2015

/cc @silvolu

@stephenplusplus
Copy link
Contributor Author

Looks like we just need to re-generate the key: npm/npm#8970 (comment)

@silvolu
Copy link
Contributor

silvolu commented Jul 31, 2015

@jgeewax it's probably better if you do it adding your key?

@jgeewax
Copy link
Contributor

jgeewax commented Aug 3, 2015

See PR #778

@stephenplusplus
Copy link
Contributor Author

Cool, do you mind adding @callmehiphop and myself as owners?

$ npm owner add stephenplusplus gcloud
$ npm owner add callmehiphop gcloud

We have to manually publish the 0.17 tag. Travis will continue to fail since our 0.17.0 tag has the outdated .travis.yml.

@stephenplusplus
Copy link
Contributor Author

We're live on npm with 0.17.0!

@stephenplusplus
Copy link
Contributor Author

@jgeewax We're stuck again -- https://travis-ci.org/GoogleCloudPlatform/gcloud-node/builds/74461152#L3393 Could it be your session expired? We'll need another PR with updated credentials or handle it like last time with a manual npm publish in the terminal.

@jgeewax
Copy link
Contributor

jgeewax commented Aug 10, 2015

@stephenplusplus : Added you as an owner. Not sure what would have happened to my session.....

@silvolu , were you following the steps here (npm/npm#8970 (comment)) to get this working?

@stephenplusplus
Copy link
Contributor Author

@jgeewax thanks. Published 👍

@silvolu
Copy link
Contributor

silvolu commented Aug 10, 2015

@jgeewax I followed this travis guide at the time.

sofisl pushed a commit that referenced this issue Jan 17, 2023
For each client method returning a long running operation, a separate method to check its status is added.

Added methods: `checkAsyncBatchAnnotateFilesProgress`, `checkAsyncBatchAnnotateImagesProgress`, `checkImportProductSetsProgress`, `checkPurgeProductsProgress`.
sofisl pushed a commit that referenced this issue Sep 13, 2023
* docs: changing format of the jsdoc links

PiperOrigin-RevId: 509352615

Source-Link: googleapis/googleapis@b737d30

Source-Link: googleapis/googleapis-gen@8efadf3
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiOGVmYWRmM2Q1ODc4MGVhMWM1NTAyNjhkNDZhM2RjNzAxYmEzN2ZjZiJ9

* 🦉 Updates from OwlBot post-processor

See https://github.com/googleapis/repo-automation-bots/blob/main/packages/owl-bot/README.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
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

Successfully merging a pull request may close this issue.

3 participants