testing and snapshot envs are down again again because of failed BE build and snapshot-stable env is stale because of failed auto tests
there are several proposals for test and snapshot envs:
1. roll back to the previous build version in case a new build is failed. In this case we'll always have working environments, but with a bit stale code (~1 day) - IMO it's not a big problem. plus dashboard shows what version is deployed - it will avoid confuses together with #2
2. notify devs that build is failed (it can be push notification in slack, email or smth like that) they can react.
plus snapshot-stable env
1. should have the last successful snapshot build (doesn't matter automation tests are failed or passed zburke JohnC what do you think? IMO we are interested in test reports that can be reviewed by anyone), because automation are usually failed because of timeouts etc that's not related to the functionality.
2. send test report to devs in case automation is failed