docs/tutorials/using-recall-with-ci/cd-pipelines

Advanced15 min

Using recall with CI/CD pipelines

Store deployment commands in recall and run them from GitHub Actions, GitLab CI, or any CI system.

Why use recall in CI/CD?

✓Store complex deployment commands outside your codebase

✓Update deploy commands without changing workflow files

✓Share deploy scripts across multiple repos

✓Audit who changed what command and when

01Set up recall in CI

In pipelines you typically use the native installer or npm. The VS Code extension is for local editing; it does not replace a CLI in headless runners.

Option A — native (GitHub Actions, Linux runner)

- name: Install recall run: curl -fsSL https://devkitvault.com/recall/install.sh | sh- name: Authenticate run: echo "${{ secrets.RECALL_TOKEN }}" > ~/.recall/token

Option B — npm (after setup-node)

- uses: actions/setup-node@v4 with: node-version: 20- run: npm install -g @devkitvault/recall- name: Authenticate run: echo "${{ secrets.RECALL_TOKEN }}" > ~/.recall/token

Option C — VS Code: for local workflows use the recall VS Code extension. See also /docs/install.

02Store your deploy command

recall save "kubectl set image deployment/app app=myrepo/app:latest -n production" --name deploy-app --tags deploy,k8s

03Call it from your pipeline

.github/workflows/deploy.yml

- name: Deploy run: recall run deploy-app

To update the deploy command, change it in recall — no PR needed on your workflow file.

Get your token for CI

cat ~/.recall/token# Copy this value to your CI secrets as RECALL_TOKEN

// what's next

→ Save multi-line deploy scripts as snippets → Load environment variables in CI