CLI: expose NX_BAIL as env variable in order to configure --nxBail

[Hotell]

To follow nx CLI configuration setup via global env variables it would be really helpful to add variable to set --nxBail argument.

we want this behaviour in all our pipelines and ATM it adds unnecessary churn to the whole CI setup (example

Current:

will bail on 1st failed build target execution

nx affected -t b --nxBail

Expected:

## ADO pipeline config
variables:
  NX_BAIL: true

will bail on 1st failed build target execution

nx affected -t build

[100terres]

That would be a super useful environment variable.

I'm working on a project with many commands that use --nx-bail. We sometimes want to run everything even on failure, but it's a bit of a pain to edit the GitHub action workflow file and remove this flag from the different commands.

To make this easy, we've added a workflow_dispatch event with an input that lets us disable the bail flag and run everything without changing the workflow file. However, since we can't set an environment, our config is a bit complex.

It would greatly simplify our setup if we could do the following:

env:
  NX_BAIL: ${{ inputs.activate_nx_bail }}

[jase88]

#34711