Migrate CI/CD pipelines from Concourse to GitHub Actions

Overview

We're currently running our CI/CD pipelines on Concourse, but GitHub Actions has matured significantly and would give us several advantages for this project. It's worth evaluating a migration.

Why Consider This?

• Tighter Integration: Everything lives in GitHub now. No need to manage a separate CI/CD tool.
• Simpler Maintenance: Fewer external systems to keep running and monitoring.
• Cost: We could reduce infrastructure costs by consolidating.
• Faster Feedback: Same platform where we're already reviewing code.
• Team Efficiency: Developers already familiar with GitHub; less context switching.

What We'd Need to Do

1. Document our current Concourse pipeline configuration and what each step does
2. Create the new workflows in a branch before switching
3. Test the new workflows
4. Plan a cutover strategy (maybe run both in parallel for a bit)
5. Update any documentation that references Concourse

Current Scope

This would cover:

• All automated testing pipelines
• Build and artifact generation
• Deployment workflows
• Any scheduled jobs we currently run on Concourse

Next Steps

• Audit what's running in Concourse and document the details
• Spike out a few workflows in GitHub Actions to see if the feature set works for us
• Get team feedback on the approach

Start by auditing the current Concourse pipeline configuration and documenting what each step does. Then compare a few GitHub Actions workflows against the testing, build, artifact, deployment, and scheduled-job requirements; the work is done when the workflows are tested, a cutover plan is agreed, and Concourse references are updated.