Continuous Integration with Docker

One of the several benefits of using containers centers around your ability to build a container at the development stage, and promote it through each environment to production. This strategy keeps environments consistent throughout each environment, and allows close-to-production testing to be done earlier. Coupling this benefit with your existing Continuous Integration pipeline will provide a more consistent deployment process from beginning to end.

1. Developer commits code to version control
2. Continuous Integration tool (Jenkins) triggers on check-in, tests the changes, and builds a Docker Image
3. Jenkins submits new version of Image to Registry
4. Docker Container is built and executed on QA server for testing
5. Testing begins in Non-Prod / Prod environments
6. Container is promoted to Staging server after successful tests
7. Container is promoted to “Blue” Production environment (non-live) after successful tests
8. Container is promoted to “Green” Production release, after successful tests, and is live
9. User access new functionality