-
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option to turn off progress logging #2012
Labels
P5
The team acknowledges the request but does not plan to address it, it remains open for discussion
Comments
filipesilva
added
type: enhancement
P5
The team acknowledges the request but does not plan to address it, it remains open for discussion
labels
Sep 19, 2016
+1 because it is really bothering when ng build is run in continuous integration |
victornoel
added a commit
to victornoel/angular-cli
that referenced
this issue
Oct 21, 2016
Fix angular#2012 Use ng build --no-progress to disable the progress bar.
victornoel
added a commit
to victornoel/angular-cli
that referenced
this issue
Oct 21, 2016
Fix angular#2012 Use ng serve --no-progress to disable the progress bar.
victornoel
added a commit
to victornoel/angular-cli
that referenced
this issue
Oct 21, 2016
Now use `ng build --no-progress` to disable the progress information. Closes angular#2012
victornoel
added a commit
to victornoel/angular-cli
that referenced
this issue
Oct 21, 2016
Now use `ng serve --no-progress` to disable the progress bar. Closes angular#2012
victornoel
added a commit
to victornoel/angular-cli
that referenced
this issue
Oct 22, 2016
Now use `ng serve --no-progress` to disable the progress bar. Closes angular#2012
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this issue
Oct 27, 2016
Currently builds output a lot of information, some of which can hide errors, by default. This PR cuts down on the information shown and adds a `--verbose` flag to restore previous build output. A `--progress` flag is also present to turn off progress logging in CI environments. Fix angular#1836 Fix angular#2012
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this issue
Oct 27, 2016
Currently builds output a lot of information, some of which can hide errors, by default. This PR cuts down on the information shown and adds a `--verbose` flag to restore previous build output. A `--progress` flag is also present to turn off progress logging in CI environments. Fix angular#1836 Fix angular#2012
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this issue
Oct 27, 2016
Currently builds output a lot of information, some of which can hide errors, by default. This PR cuts down on the information shown and adds a `--verbose` flag to restore previous build output. A `--progress` flag is also present to turn off progress logging in CI environments. Fix angular#1836 Fix angular#2012
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this issue
Nov 24, 2016
Currently builds output a lot of information, some of which can hide errors, by default. This PR cuts down on the information shown and adds a `--verbose` flag to restore previous build output. A `--progress` flag is also present to turn off progress logging in CI environments. Fix angular#1836 Fix angular#2012
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this issue
Nov 26, 2016
Currently builds output a lot of information, some of which can hide errors, by default. This PR cuts down on the information shown and adds a `--verbose` flag to restore previous build output. A `--progress` flag is also present to turn off progress logging in CI environments. Fix angular#1836 Fix angular#2012
filipesilva
added a commit
that referenced
this issue
Nov 30, 2016
* feat(build): add --verbose and --progress flags Currently builds output a lot of information, some of which can hide errors, by default. This PR cuts down on the information shown and adds a `--verbose` flag to restore previous build output. A `--progress` flag is also present to turn off progress logging in CI environments. Fix #1836 Fix #2012
MRHarrison
pushed a commit
to MRHarrison/angular-cli
that referenced
this issue
Feb 9, 2017
* feat(build): add --verbose and --progress flags Currently builds output a lot of information, some of which can hide errors, by default. This PR cuts down on the information shown and adds a `--verbose` flag to restore previous build output. A `--progress` flag is also present to turn off progress logging in CI environments. Fix angular#1836 Fix angular#2012
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
P5
The team acknowledges the request but does not plan to address it, it remains open for discussion
OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Any
Versions. Please run
ng --version
. If there's nothing outputted, please runin a Terminal:
node --version
and paste the result here:1.0.0-beta.11-webpack.8
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
Stock CLI app. Run
ng build
. See progress.The log given by the failure. Normally this include a stack trace and some
more information.
Mention any other details that might be useful.
This is mostly for running builds as part of a CI. Logging makes a mess and doesn't work properly when displayed outside of a terminal. Normally when using straight webpack, you'd just pass along the
--no-progress
option.The text was updated successfully, but these errors were encountered: