Error behaviour for when a parallel faas-cli build fails

This issue discusses error behaviour for when a parallel faas-cli build fails.

I was building the samples in the main faas repo using the YAML file, one of them failed and printed red text but it was really hard to see and I could have missed it.

I thought we had already done work to break out upon an error and give a non-zero exit code.

How do we want this to work?

Scenario 1 - sequential

You're building 5 functions sequentially from a YAML file - number 3 fails, should we break out and stop?

Scenario 2 - parallel

You're building the same stack with --parallel=4 and output is intermingled. Do we break out all builds as soon as one of them produces an error?

Solutions

• Break out of either flow upon first error
• Push on and summarise a list of functions built in an ASCII table:

Other considerations

Headless use of faas-cli build in CI

@developius @itscaro @rgee0

Start by reproducing the failure with faas-cli build using the YAML file, both sequentially and with --parallel=4. Review the existing build entry points and error handling, then clarify the desired stop-or-continue behavior, summary output, and non-zero exit status before implementation.