The nice thing is that a pipeline is saved in the project itself (in a file called Jenkinsfile). This means your whole team can see how the build works and update it when needed.

Pipelines can also be flexible:

• For small changes, Jenkins can run only quick checks;

• For bigger updates, it can run more tests or even deploy the app.

So, a pipeline is not just "build–test–deploy", it’s a set of rules you control to make sure every change is safe before reaching users.

Steps to Create a Jenkins Pipeline

Now, let's create a Jenkins pipeline — a structured series of automated steps that move our code from development to deployment.

Quick Summary from the Video:

1. Log in to Jenkins;

2. Create a new item: click New Item, enter your project name, and choose Pipeline as the project type;

3. Configure the pipeline:

   • In the Pipeline section, choose Pipeline Script (manual) or Pipeline Script from SCM to pull the Jenkinsfile from your repository.

4. Connect to your GitHub repository:

   • Under Definition, select Pipeline Script from SCM;

   • Set SCM to Git, paste your repository URL, and provide your GitHub credentials (using the Personal Access Token);

   • Make sure the pipeline is connected to the main branch.

5. Save and run: click Save, then Build Now to test the pipeline setup. You can watch each stage run in real time.

You've now successfully set up a Jenkins pipeline and connected it to GitHub using a Personal Access Token. With this configuration, your pipeline can automatically pull code, build it, run tests, and deploy updates whenever changes are pushed — creating a fully automated CI/CD workflow.