Over the last several years, the terms CI/CD (continuous integration, continuous deployment) and DevOps (development and operations) have grown to be known throughout most of the software industry. The implication of these practices is that no longer must software wait for a "release ritual" to push a new version to production. Nor must software be developed by one team and then "handed over" to a production support team.
Instead, now a development team manages the software from end-to-end:
- Requirements
- Code changes
- Testing
- Build and package artifacts
- Deploy to production
- Support
Also, software has seen a much quicker release cycles. It is even possible to have pipelines that perform releases and deployments upon every committed code change.
Throughout the next few posts, we will build a fully automated CI/CD pipeline for a simple REST service. The series will be broken down into individual posts:
- Introduction (this post)
- Base application
- CI for testing
- Dockerizing the application
- Product acceptance testing (PATs)
- CD for deployment
The tools we will be working with throughout this project will be:
