Jenkins to GitHub Actions path - Step-by-Step Execution

Process Flow - Jenkins to GitHub Actions path

Start: Jenkins Pipeline

↓

Identify Jenkins Steps

↓

Map Steps to GitHub Actions

↓

Create GitHub Workflow YAML

↓

Test GitHub Actions Workflow

↓

Fix Issues & Optimize

↓

Complete Migration

This flow shows the step-by-step path to move a Jenkins pipeline to GitHub Actions by identifying steps, mapping them, creating workflows, testing, and finalizing.

Execution Sample

Jenkins

pipeline {
  agent any
  stages {
    stage('Build') {
      steps { sh 'make build' }
    }
  }
}

A simple Jenkins pipeline that runs a build command in a stage.

Process Table

Step	Action	Jenkins Part	GitHub Actions Equivalent	Result
1	Start with Jenkins pipeline	pipeline { agent any ... }	N/A	Ready to migrate
2	Identify stages and steps	stage('Build') { steps { sh 'make build' } }	Map to jobs and steps	Build stage identified
3	Map 'sh' step	sh 'make build'	run: make build	Shell command mapped
4	Create GitHub workflow YAML	N/A	jobs: build: runs-on: ubuntu-latest steps: - run: make build	Workflow file created
5	Test GitHub Actions workflow	N/A	Trigger workflow on push	Build runs successfully
6	Fix issues if any	N/A	Adjust YAML or commands	Workflow stable
7	Complete migration	Jenkins pipeline deprecated	GitHub Actions active	Migration done

💡 Migration complete when GitHub Actions workflow runs successfully and Jenkins pipeline is retired.

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
Pipeline Code	Jenkins pipeline script	Stages identified	GitHub Actions YAML created	GitHub Actions workflow active
Build Command	sh 'make build'	Mapped to run step	In YAML as run: make build	Runs successfully in GitHub Actions

Key Moments - 3 Insights

Why do we need to map Jenkins 'sh' steps to GitHub Actions 'run' steps?

Because Jenkins uses 'sh' to run shell commands inside its pipeline, while GitHub Actions uses 'run' steps in YAML to execute shell commands. This mapping ensures the same commands run correctly in the new system, as shown in execution_table row 3.

What happens if the GitHub Actions workflow fails during testing?

You need to fix the YAML or commands and retest until it runs successfully. This iterative process is shown in execution_table row 6.

Can we run Jenkins and GitHub Actions pipelines simultaneously during migration?

Yes, initially you run both to verify the GitHub Actions workflow works before retiring Jenkins, as implied between steps 5 and 7.

Visual Quiz - 3 Questions

Look at the execution table, what is the GitHub Actions equivalent of the Jenkins 'sh' step?

A command: make build

B shell: make build

C run: make build

D execute: make build

💡 Hint

Check execution_table row 3 for the mapping of Jenkins 'sh' to GitHub Actions.

At which step does the GitHub Actions workflow get created?

A Step 2

B Step 4

C Step 5

D Step 7

💡 Hint

Look at execution_table row 4 describing workflow YAML creation.

If the build command changes, which part of the variable_tracker will update?

A Build Command

B Pipeline Code

C Final

D Start

💡 Hint

Refer to variable_tracker row for 'Build Command' showing command changes.

Concept Snapshot

Jenkins to GitHub Actions migration:
1. Identify Jenkins pipeline stages and steps.
2. Map Jenkins steps (like 'sh') to GitHub Actions 'run' steps.
3. Write GitHub Actions workflow YAML.
4. Test and fix workflow.
5. Retire Jenkins pipeline after successful migration.

Full Transcript

This visual execution shows how to migrate a Jenkins pipeline to GitHub Actions. We start by identifying Jenkins pipeline stages and shell commands. Then we map these steps to GitHub Actions YAML syntax, replacing 'sh' with 'run'. Next, we create the GitHub Actions workflow file and test it by triggering runs. If issues appear, we fix and retest until stable. Finally, we retire the Jenkins pipeline once the GitHub Actions workflow runs successfully. Variables like pipeline code and build commands update step-by-step during migration. Key moments include understanding step mapping, testing workflows, and running both pipelines during transition.