In order to setup automated deployments we need automated testing of the deployed stack.
Closed this issue · 5 comments
Natim commented
I guess it might be good enough to call:
- once all the checks
- once the heartbeat endpoint
magopian commented
Can you give more context please? Are you talking about a travis (or another CI) integration here?
But there's already travis, so I don't understand what "automated testing" means?
Natim commented
We are talking about a Jenkins job to validate the stack, something like: https://github.com/Kinto/kinto-integration-tests
mostlygeek commented
It's on ops/qa to automate the deployment and promotion. We should be focused primarily on:
- making sure
__heartbeat__is good / reliable way to monitor the service. Though I'm not sure what that really means. Pollbot only breaks when the things it checks are down or changed in ways we haven't anticipated. - making we automate container publishing with circleci, (Dockerflow)
Natim commented
Both dots are already covered.
I think mocking the delivery-dashboard and calling all checks ones for the current supported product channels might be a good way to validate that everything works properly.