Set fail-fast to true in upstream zuul project

[amartyasinha]

fail-fast allows us to fail the entire pipeline the moment any job from the pipeline fails. Currently, we have to wait for all jobs to return their status for the pipeline to get complete. It wastes compute resoures as well as time.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/182390de39f54ed4aaea7f7e84b43d61

⚠️ openstack-k8s-operators-content-provider CANCELED
⚠️ podified-multinode-edpm-deployment-crc CANCELED
⚠️ cifmw-crc-podified-edpm-baremetal CANCELED
❌ cifmw-pod-zuul-files FAILURE in 5m 02s
✔️ noop SUCCESS in 0s
⚠️ cifmw-pod-ansible-test CANCELED
⚠️ cifmw-pod-pre-commit CANCELED
⚠️ build-push-container-cifmw-client CANCELED

[dasm]

FTR: https://zuul-ci.org/docs/zuul/latest/config/project.html#attr-project.%3Cpipeline%3E.fail-fast

@amartyasinha thank you for the PR. I approved it initially, because that looks solid. Now I need to remove my approval.
I'd like to hear from CI-DevOps team to see how we're moving forward with CI-FMW promotions.

[danpawlik]

I'm just concerned, that If that is enabled, post job would not be executed in other job. It means, that infra cleaner needs to be executed more often.

[amartyasinha]

I had enabled auto-merge, and seems like it got merged. Let's see if it is impacting promotions or infra cleaning. If it happens, we can revert this change.