Skip to content

Continuous Integration with Docker

Robert Greiner
Robert Greiner
1 min read
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
Please consider subscribing, it's free.
Technology

Robert Greiner Twitter

Professional optimist. I write a weekly newsletter for humans at the intersection of business, technology, leadership, and career growth.


Related Posts

Members Public

Navigating the Upside Down as a Technology Leader

Ideas for leading technology organizations with confidence and creativity.

Navigating the Upside Down as a Technology Leader
Members Public

Artist for a Day

The future of creative output is multiplied by AI.

Artist for a Day
Members Public

The Auto Industry's Cloud Awakening

Auto manufacturers are behind the cloud adoption curve but are well-positioned to unlock the future of mobility by building foundational capabilities across six key areas.

The Auto Industry's Cloud Awakening