Once you have integration tests, getting something operational to validate those tests is very important. If you don't run the tests, they're effectively useless—so having a means of consistently invoking the tests while you're doing development is important. It is fairly common to see continuous integration do a lot of the automated lifting for development.
There are a number of options available to development teams to help you with continuous integration, or even its more advanced cousin, continuous deployment. The following tools are an overview of what was available at the time of writing, and in use by developers working with their code in containers and/or in Kubernetes:
- Travis.CI: Travis.CI ...
