Microservices build pipeline

Microservices could also be built and tested using the popular CI/CD tools such as Jenkins, TeamCity, and so on. It is very similar to how a build is done in a monolithic application. In microservices, each microservice is treated like a small application.

For example, once you commit the code in the repository (SCM), CI/CD tools trigger the build process:

• Cleaning code
• Code compilation
• Unit test execution
• Contract/Acceptance test execution
• Building the application archives/container images
• Publishing the archives/container images to repository management
• Deployment on various Delivery environments such as Dev, QA, Stage, and so on
• Integration and Functional test execution
• Any other steps

Then, release-build triggers that change the SNAPSHOT or RELEASE version in pom.xml (in case of Maven) build the artifacts as described in the normal build trigger. Publish the artifacts to the artifacts repository. Tag this version in the repository. If you use the container image then build the container image as a part of the build.