-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Private packages not working on TravisCI #1208
Comments
I have some problem with our private registry based on Sinopia. |
Experiencing the same thing with our private registry, but not just on CI - locally as well. |
Experiencing same problem with private artifactory |
I removed the local yarn cache and it solved the issue |
Clearing the cache didn't help our issue - still getting 'invalid tar file' which normally means the auth token is not being sent correctly. |
Here is our trace, if it is any help:
|
i have a fix for this at bdentino@558850a. if i can get a second opinion that it works for others and isn't likely to cause a regression i'll probably submit a PR. |
I have this issue as well. macOS 10.12.1
I attempted @bdentino's fix and received the same stack trace with the same error |
@vinnymac for me the root cause of the 'invalid tar file' error was that authentication headers weren't properly being sent with the request. are you able to confirm whether or not your issue is related to authentication by logging out the status code of the actual request to |
@bdentino my mistake, whatever the problem was it seems to be resolved now. I had an issue with this, and for some reason everything is working today. I had a separate issue with private github installs. Which I fixed by doing |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Running
yarn
from within TravisCI fails at the "fetching packages" step. See output below.If the current behavior is a bug, please provide the steps to reproduce.
NPM_TOKEN
appropriately set as env variable).What is the expected behavior?
Running
yarn
should successfully download all packages.Please mention your node.js, yarn and operating system version.
Output from
yarn-error.log
(manifest/lock file excluded for brevity):Here's my
travis.yml
(adapted from https://github.com/javascriptair/site/blob/master/.travis.yml):.travis.npmrc
is:NOTE: This same configuration works when building/installing on TravisCI with
npm
.The text was updated successfully, but these errors were encountered: