Make CMBR fail with a proper exit code
Summary
We recently had an incident when we completely lost Delivery UAT instance. We also have CMBR job running on a schedule. During the incident CMBR job kept running, but CMBR application didn't fail on connection timeout.
What needs to be done?
- Properly define CMBR error codes and fail with non-zero exit status in case of critical failure
- Modify CMBR job definition if it's necessary to reflect CMBR exit status
Links
Edited by Vladimir Glafirov