Jenkins+Docker continuous integration flowchart

Introduction:

In the Internet age, for every company, the importance of software development and release is self-evident. A set of standard processes has been formed, and the most important components are continuous integration (CI) and continuous deployment and delivery (CD). This article is based on Jenkins+Docker+Git to implement a set of CI automated publishing process.

Traditional workflow:

1. Java project development
2. Submit the project code to (git or svn)
3. Pull the project code (jenkins or manual)
4. Compile the project code (jenkins or manual)
5. Publish the java project and run the java project
6. Test

Automated workflow:

1. Developers submit code to the Git version repository;
2. Jenkins manual/timing trigger project construction;
3. Jenkins pulls the code, code encoding, packaged images, and pushes to the mirror repository;
4. Jenkins creates a container on the Docker host and releases it.