CircleCI Ideas

Allow Job Failures

Use Case: 
We have some Jobs in our workflows, eg linting of code. If these fail the whole workflow shows as Failing, forever. Is there any way we can mark certain Jobs as not important? Would be nice if these non-important jobs would show with status= warning and not failed.

Similar (but not the same) as: 
https://circleci.com/ideas/?idea=CCI-I-216

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 21 2018
  • New
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    November 08, 2018 10:55

    We have a large application with an important dependency. To be prepared (just as a warning) we want our application to be tested with coming releases of that dependency (beta and canary). It doesn't matter for the current state of our application, so it may not fail and should deploy it. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    November 08, 2018 11:09

    So the overall test won't fail, but you would be able to see whether a job is failing.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    28 Feb 17:32

    This would be very useful for integrating long-running or partially-passing test suites. We are building a browser test suite but the run times will never be acceptable for every build. We'd like to run them intermittently, but only warn that they failed, not fail the whole build.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    06 Mar 19:43

    +1 for warnings

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    30 Mar 14:58

    I agree with this. Having a warning status would add more flexibility to our CI processes and would allow us to communicate non-critical issues to our developers in a less disruptive manner.