-
Notifications
You must be signed in to change notification settings - Fork 12k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
The analytics prompt shouldn't run in CI environments #14563
Comments
You can set this flag in your CI to disable the analytics. We'll work on fixing this in the next patch release. |
Awesome, thanks @mgechev! btw it might be worth documenting the |
I also have this issue. For info: it appeared during the CLI beta phase, then was fixed (it was OK in CLI v8.0.0-rc.4), and is here again in v8.0.0, so a commit between v8.0.0-rc.4 and 8.0.0 reintroduced this issue. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
馃悶 Bug report
Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was:v7 and below
Description
When upgrading to v8 the analytics prompt breaks CI as it hangs infinitely waiting for the user to choose to enable it or not
馃敩 Minimal Reproduction
Run npm install on a v8 cli project on CI. For example: https://travis-ci.org/mattlewis92/angular-calendar/builds/538499347
Attempting to disable analytics on the project then fails as the config it adds to angular.json is invalid
馃敟 Exception or Error
馃實 Your Environment
Anything else relevant?
The
is-ci
package could be used to disable that prompt on CI envs: https://www.npmjs.com/package/is-ciThe
analytics
config needs to be added to the schema so it can be disabled at the project levelThe workaround for now is to add this to travis.yml
The text was updated successfully, but these errors were encountered: