Jenkins to GitHub Actions Migration

Point this agent at your Jenkins-built repositories and ask it to plan the move to GitHub Actions.

What it does

1. Map your Jenkins footprint (Jenkinsfiles, shared libraries, plugin usage, credentials bindings, triggers) and tier each pipeline as mechanical, rework, or redesign
2. Plan a phased migration: inventory → translate → parallel-run → cutover, including a credentials-to-secrets migration plan
3. Generate .github/workflows/*.yml files with stage→job, agent→runs-on, credentials()→secrets, and parallel→matrix translation
4. Sandbox — push generated workflows to a sandbox repository, trigger workflow_dispatch runs, and report PASS/PARTIAL/FAIL evidence with run URLs

Prerequisites

• GITHUB_TOKEN — fine-grained PAT with repo + workflow scope on a sandbox repository
• GITHUB_TEST_REPO — owner/repo sandbox repository the agent may push workflow runs to
• JENKINS_URL — optional; base URL of the Jenkins controller for read-only job enumeration
• JENKINS_API_TOKEN — optional; read-only API token for job inventory and parallel-run diffing

Current scope

This solution translates declarative Jenkins pipelines and plans the migration of scripted ones. It does not auto-translate arbitrary Groovy in scripted pipelines, does not move secret values out of Jenkins credentials stores (it produces a checklist — you copy the values), does not migrate Jenkins controller/agent infrastructure, and does not configure self-hosted runners.