-
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
Build fail on ERROR #2014
Comments
This is a bug actually. We should have a non-zero exit code for failed builds. |
This would be great, I just experienced the same thing. Are there any workarounds we can do ourselves in the meantime? |
Seems related to webpack/webpack#708 |
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. |
Hy,
is it somehow possible to make a complete build fail if there is a error during the build?
My situation is the following: I have a CI setup that builds my project, wraps it into a docker and publishes it into a docker repo. If I then want to publish a the new version I use docker to pull the new image and run it. Recently I did exactly that to then discover that the app doesn't work. Looking trough the CI server logs I found out that the production build of angular-cli (beta webpack 8) had an ERROR message, but it did not fail the build. If it would have than no new docker image would have been published and I would have noticed before I published the new version.
Thanks and Greetings
The text was updated successfully, but these errors were encountered: