Re-write container pipeline service CI engine #530
Description
The current container pipeline ci is very tightly coupled with CICO. This should not ideally be the case.
We need more separation of concerns.
What we want is
- Provisioning of the service should not be part of CI code. It can be invoked by CI, and fail if it fails, when its needed, but should not be built into it.
- A CI, that just runs tests, given the nodes, without worrying about how they were provisioned.
- A CI, that allows us to run targeted tests. I may not want sit through entire provision if i just did a minor change to code base, I want to test against that change. In cases where it needed, we can rsync code, and trigger parts of provisioning to maybe re-deploy containers, as needed.