Product update

Bring Your Own CI to Wodby: GitHub Actions and GitLab CI

Wodby now supports GitHub Actions and GitLab CI as third-party CI integrations, so teams can keep their existing pipeline workflow while using Wodby for stack-aware Kubernetes delivery.

Wodby CI remains the fastest built-in path for many projects, but not every team wants to move release automation out of the system where code review, branch policies, approvals, and deployment gates already live. With third-party CI support, your pipeline can call Wodby CLI directly and still use the same Wodby build, release, and deployment model.

How it fits into Wodby

Create a GitHub or GitLab integration in Wodby with the right provider kind for Git and CI. When creating a new app, choose GitHub Actions or GitLab CI as the CI integration on the first step. On the build source step, connect the GitHub or GitLab repository for every buildable app service that should be built by your pipeline.

From there, add a Wodby API key to your CI provider, initialize the build with the buildable app service ID, then let Wodby CLI handle the rest:

  • wodby ci init creates or loads the Wodby build and logs in to the registry.
  • wodby ci run can run dependency installation or other one-off commands inside the stack build context.
  • wodby ci build builds one or more app service images.
  • wodby ci release pushes those images to the configured registry.
  • wodby ci deploy deploys the released images back to the Wodby app instance.

Wodby CLI submits build metadata from the CI environment back to Wodby, including provider, commit, ref, build number, workflow or run identifiers, and post-deployment script information. That metadata powers build status tracking today and prepares the same integrations for dashboard-triggered builds in the future.

GitHub Actions

The GitHub integration is built on the Wodby GitHub App. During app installation, you control which GitHub accounts and repositories the app can access. GitHub Actions workflows can install and initialize Wodby CLI with wodby/actions/setup-wodby-cli@v1. Wodby tracks the workflow run as the external build, and future dashboard-triggered builds will depend on the workflow supporting workflow_dispatch and the GitHub App having Actions permissions for the repository.

See the step-by-step guide: Deploy to Kubernetes from GitHub Actions with Wodby.

GitLab CI

GitLab CI pipelines can run Wodby CLI from the official CLI image and use Docker-in-Docker for image builds. GitLab.com integrations can use OAuth2 or token authentication. Token authentication also works for GitLab.com and is the supported option for self-hosted GitLab, where you provide the GitLab base URL.

GitLab tracking maps to GitLab's pipeline and job model: Wodby stores pipeline metadata and tracks the job that produced the build. That gives Wodby enough context for status tracking today and dashboard-triggered GitLab builds in the future.

See the step-by-step guide: Deploy to Kubernetes from GitLab CI with Wodby.

Start from the pipeline you already use

If your team already has build checks, protected branches, or release approvals in GitHub or GitLab, keep that control plane and add Wodby only where it matters: stack-aware builds, image release, and Kubernetes deployment.

Example pipeline files for supported CI providers are available in github.com/wodby/wodby-ci.