Skip to content
excalibase
pipelines
Pipelinesbeta

Pipelines

Your CI builds the image and pushes it to your registry. Excalibase deploys that image to a container app by its digest, so what runs is exactly what CI built. Excalibase does not build your code: building on a plain git push is planned, not available.

How it works

  1. CI builds the image and pushes it to your registry (GHCR, GitLab, Docker Hub or a private registry).
  2. A final step calls the app's deploy API with the image digest and the commit.
  3. Excalibase rolls the app out and the step waits until the deploy succeeds or fails.

Set it up in Studio

Open your container app in Studio and choose its Pipeline tab. Under Deploy from CI:

  1. Create an access token with write access, bound to this project, and keep it in your CI as a secret named EXCALIBASE_TOKEN (in Jenkins, a secret text credential with the ID excalibase-token).
  2. If the image is in a private registry, save a registry credential for it under Containers.
  3. Copy the ready-made file for your CI, pre-filled with your project, app and image: GitHub Actions (.github/workflows/deploy.yml), GitLab CI (.gitlab-ci.yml) or a Jenkinsfile. Any other CI uses the same curl step.

Each file builds on a push to your branch, pushes the image, then deploys it and waits until the app's URL is live; the job fails when the deploy does. You can set the build folder, the Dockerfile path and the branch.

Your AI coding tool can write the same files: the MCP tool get_ci_snippet returns the same pipeline, and get_dockerfile_template returns a Dockerfile for your stack.

GitHub Actions

The action is on GitHub Marketplace: Deploy to Excalibase.

The workflow builds and pushes with the Docker actions, then deploys the pushed digest with excalibase/deploy-action:

name: Deploy to Excalibase
on:
  push:
    branches: ["main"]
permissions:
  contents: read
  packages: write
concurrency: excalibase-deploy
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: docker/setup-buildx-action@v4
      - uses: docker/login-action@v4
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
      - id: build
        uses: docker/build-push-action@v7
        with:
          context: "."
          push: true
          tags: ghcr.io/you/app:main,ghcr.io/you/app:${{ github.sha }}
      - uses: excalibase/deploy-action@v1
        with:
          app: <projectId>/<appId>
          image: ghcr.io/you/app@${{ steps.build.outputs.digest }}
          token: ${{ secrets.EXCALIBASE_TOKEN }}

The deploy call

GitLab CI, Jenkins and any other CI end with one request to the app's deploy route, after pushing the image:

curl --fail-with-body -sS -X POST "https://app.excalibase.io/api/projects/<projectId>/apps/<appId>/deploy?wait=true" \
  -H "Authorization: Bearer $EXCALIBASE_TOKEN" \
  -H "Content-Type: application/json" \
  -d "{\"image\":\"$IMAGE\",\"commitSha\":\"$COMMIT_SHA\"}"

With wait=true it answers once the deploy has finished: 200 with the deploy when it is live, 422 when it failed (the reason is in error), 409 when a newer deploy replaced it, and 504 when it is still rolling out after 11 minutes (it carries on: poll .../deploys/<id>). --fail-with-body makes every answer but 200 fail the step and print why. Without wait it answers 202 with the deploy's id at once.

Deploy history, redeploy and roll back

The Pipeline tab lists every deploy with its source (Studio, CI with the commit, or the image watcher), the image and digest it ran, its duration and its logs. You can redeploy, and roll back to an earlier revision: it runs that revision again with the settings it had then. Database migrations are not touched by a roll back.

Auto-deploy

As an alternative to a CI step, switch on Auto-deploy when the image tag changes. Every few minutes Excalibase looks the tag up in its registry, and when it points at a new digest, that digest is deployed. An image pinned by digest never changes, so name a tag to use it.

Planned

Building on Excalibase's side from a plain git push is not available yet. See the roadmap.