arrow_back
Back

Continuous integration: Jenkins, Travis, CircleCI, and containers

Andrew Dorokhov Andrew Dorokhov schedule 1 min read
menu_book Table of Contents

Continuous integration (CI) automates building and testing code on every change. Options fall into self-hosted and hosted services.

Self-hosted

Hosted services

Most of these tools focus on running unit tests for a predefined set of programming languages rather than full container-based test orchestration. That said, all of the vendors above have shown growing interest in containerization.

Containers in CI/CD

Containers fit CI/CD workflows well. The main idea: use the same image across pipeline stages instead of rebuilding environment-specific images at each step. Build once, run tests, deploy — all from one artifact.

code

Need Help with Development?

Happy to help — reach out via the contacts or go straight to my Upwork profile.

work View Upwork Profile arrow_forward