Mark skipped job with gray icon
J
Jay Carlton
I have a few workflows where we evaluate a branch for changed paths and do a circleci step halt if there are no hits. This works well enough, but the issue is that in the UI the job containing step is still marked in green (as is the skipped job). Ideally we would have a halt syntax that allowed recording a success, failure, or new (as far as I can tell) "skipped" state for the jobs that didn't run for a particular invocation (e.g. a PR changeset).
CCI-I-1496
t
tyler@datachat.ai
This is a great way to show that a job isn't applicable without giving the misleading impression that it ran its full logic and was completely successful.
For my use-case, I would much prefer to have a special
when
attribute on job invocations to provide conditional logic, but having a "skipped" status is a good compromise and has benefits of its own as well.The four job statuses that I think are extremely valuable and flexible are:
- success
- failure
- skipped (job is not applicable, don't fail pipeline, don't imply success)
- warning (job deserves attention, but don't fail pipeline)
Julien Bourdeau
One example, I'd use this for slack notification step. If they fail, I don't want to halt the build but I don't want to mark it as success either.