Command Palette

Search for a command to run...

GitHubGitHub

CI/CD Automation

Set up GitHub Actions, GitLab CI and Jenkins with pipeline examples, runner configuration, caching strategies and deployment automation you can copy straight into your projects.

Continuous integration and delivery turns a manual release process into a repeatable, auditable pipeline. These guides walk you through installing each platform, wiring up your first job and hardening the pipeline for production use.

Every guide is written against the current release line and verified against the upstream documentation:

GuideCurrent releaseWhat it covers
GitHub ActionsRunner v2.338.0Workflows, runners, artifacts, OIDC
GitLab CI/CDGitLab 19 / Runner 19.5.gitlab-ci.yml, rules, runners, OIDC
Jenkins2.580.1 LTSInstall, JCasC, agents, pipelines
Available Guides

GitHub Actions

GitLab CI

Jenkins

What you will learn

  • GitHub Actions — write workflows, choose the right runner, cache dependencies and reuse workflows across repositories.
  • GitLab CI — configure runners, structure jobs into stages and ship a pipeline with .gitlab-ci.yml.
  • Jenkins — install the controller and agents, unlock the setup wizard and run a first declarative pipeline.

Pipeline checklist

  1. Lint and unit test on every push
  2. Build an immutable artifact once and promote it through environments
  3. Cache dependencies to keep builds fast
  4. Store secrets in the platform secret store — never in the repository
  5. Gate deployments with approvals for production releases
OpenShift

Install OpenShift Container Platform 4.22 or OpenShift Local (CRC) for local development, install the oc CLI and deploy a production cluster with the agent-based installer.

GitHub Actions

Set up GitHub Actions with the current action versions, run your first workflow, configure GitHub-hosted and self-hosted runners and secure your pipelines with OIDC.