#95 Build pipeline vs. Release pipeline and how to combine them in Azure Devops

Before jumping directly to these 2 pipelines: Release pipeline and Build pipeline, let’s spend some time first reviewing CI/CD basics.

CI/CD

Continuous Integration/Continuous Deployment (CI/CD) is a set of principles and practices aiming at automating the whole process from integrating code changes into a shared repository, testing these code changes to deploying them to production. Let's delve into CI, CD and CI/CD pipeline next.

1. Continuous Integration (CI): From the term itself, we already have a faint clue on what it does: integrating code changes constantly. This is the process of automatic code change integration from several developers into a shared repository.

• Code Integration: Developers frequently commit their code changes to a central repository (such as Git).
• Automated Builds: CI tools automatically build the application from the latest code in the repository.
• Testing: Automated tests (unit tests, integration tests, etc.) are executed during the build process.
• Immediate Feedback: Developers receive feedback quickly if their changes break the build or fail tests. Normally, we can check from job run and error message will appear if the build fails.
• CI ensures that new code changes are continuously integrated with the existing codebase, preventing integration issues that may arise when…