High-level Process Lifecycle and Role of Pull Requests
Explore the high-level process lifecycle of applications using pull requests and feature branches within Jenkins X. Understand how automation streamlines code review, preview deployments, and validations to speed up merging and delivery. This lesson helps you grasp modern branching strategies and how Jenkins X integrates these with Kubernetes clusters for faster, more reliable CI/CD pipelines.
We'll cover the following...
Pull Requests (or whatever their equivalents are called in your favorite Git distribution) are a norm. Most of us have adopted them as the primary way of reviewing and accepting changes that will ultimately be deployed to production. They work hand-in-hand with feature branches.
🔍 Some of you might cringe thinking about pull requests. You might prefer trunk-based development, and work directly on master. Even if that is your preference, I still recommend you go through this chapter and do all the exercises. If processes were manual, getting pull requests merged would be a slow, hands-on, and time-consuming effort. If you use pull requests, you should use automation to speed up the process, and reduce the human effort required. That’s precisely what Jenkins X is doing for us. So, put your reservations about pull requests aside, and follow along.
High-level process of a lifecycle of an application
A common (and recommended) workflow is to ...