← 输入框|github.com|刷新
Skip to content

Build fail on ERROR #2014

Closed
Closed

Description

@FallenRiteMonk

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

Activity

  1. filipesilva commented on Sep 19, 2016

    @filipesilva
    Contributor

    This is a bug actually. We should have a non-zero exit code for failed builds.

  2. added
    P1Impacts a large percentage of users; if a workaround exists it is partial or overly painful
    on Sep 19, 2016
  3. self-assigned this
    on Sep 19, 2016
  4. added this to the milestone on Sep 19, 2016
  5. Blasz commented on Sep 23, 2016

    @Blasz

    This would be great, I just experienced the same thing. Are there any workarounds we can do ourselves in the meantime?

  6. filipesilva commented on Sep 26, 2016

    @filipesilva
    Contributor

    Seems related to webpack/webpack#708

  7. added a commit that references this issue on Sep 26, 2016
    b26cacf
  8. added a commit that references this issue on Sep 26, 2016
    aa48c30
  9. added a commit that references this issue on Oct 2, 2016
    26f916a
  10. added a commit that references this issue on Oct 3, 2016
    ed3ba48
  11. angular-automatic-lock-bot commented on Sep 6, 2019

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  12. locked and limited conversation to collaborators on Sep 6, 2019
  13. added a commit that references this issue on May 29, 2026
    118530c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P1Impacts a large percentage of users; if a workaround exists it is partial or overly painfultype: bug/fix

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions