Continuous integration (CI) requires developers to integrate code into a shared repository multiple times per day, with each check-in verified by an automated build to detect problems early. Continuous deployment aims to minimize lead time between writing new code and deploying it to production users, by extending CI. Docker and Jenkins can be used together for CI/CD, with Docker containerizing applications and Jenkins automating the build, test and deploy process.

1. CI/CD
Using Docker & Jenkins

2. Continuous Integration
Continuous Integration (CI) is a development practice that
requires developers to integrate code into a shared
repository several times a day. Each check-in is then
verified by an automated build, allowing teams to detect
problems early.

3. Continuous Deployment
Continuous deployment can be thought of as an extension
of continuous integration, aiming at minimising lead time, the
time elapsed between development writing one new line of
code and this new code being used by live users, in
production.

4. in a nutshell …

5. What is Docker?
Continuous deployment can be thought of as an
extension of continuous integration, aiming at
minimising lead time, the time elapsed between
development writing one new line of code and this
new code being used by live users, in production.