datarobot-oss/datarobot-agent-skills / skills/datarobot-app-framework-cicd
datarobot-app-framework-cicd
FlaggedGuidance for setting up CI/CD pipelines for DataRobot application templates using GitLab, GitHub Actions, and Pulumi for infrastructure as code. Use when setting up CI/CD pipelines, configuring deployments, or managing infrastructure for DataRobot application templates.
| File | Kind | Size |
|---|---|---|
| QUICK_REFERENCE.md | markdown | 4.0 KB |
| README.md | markdown | 6.6 KB |
| SKILL.md | skill md | 19.6 KB |
| examples/github-cd-pulumi-cloud.yml | config | 1.1 KB |
| examples/github-deploy-pulumi-cloud.yml | config | 1.3 KB |
| examples/github-destroy-pulumi-cloud.yml | config | 1.2 KB |
| examples/workflows-README.md | markdown | 3.0 KB |
| references/example-taskfile.yaml | config | 895 B |
| references/workflow-examples.md | markdown | 2.5 KB |
| scripts/decrypt-secrets.shexecutable | script | 1.2 KB |
| scripts/encrypt-secrets.shexecutable | script | 1.9 KB |
| scripts/github-cd.yml | config | 2.0 KB |
| scripts/github-deploy.yml | config | 5.0 KB |
| scripts/github-destroy.yml | config | 1.9 KB |
| scripts/gitlab-ci.yml | config | 4.7 KB |
| scripts/infra-README.md | markdown | 6.4 KB |
| scripts/pulumi-setup.shexecutable | script | 10.8 KB |
| scripts/setup-github-secrets.shexecutable | script | 3.6 KB |
| scripts/setup-gitlab-variables.shexecutable | script | 4.4 KB |
| scripts/taskfile-snippets.yaml | config | 5.6 KB |
scripts/gitlab-ci.yml
View on GitHub---
# Example GitLab CI/CD configuration for DataRobot Application Templates
# Copy this to your repository root as .gitlab-ci.yml
image: cimg/python:3.11-node
variables:
DATAROBOT_ENDPOINT: https://app.datarobot.com/api/v2
FRONTEND_TYPE: react
# ── Pulumi stack names ─────────────────────────────────────────────────────
# Set PULUMI_STACK_CI_NAME and PULUMI_STACK_REVIEW_NAME as plain CI/CD
# variables in GitLab (Settings → CI/CD → Variables) to override these
# defaults. Project variables always take precedence over the values below.
PULUMI_STACK_REVIEW_NAME: review-mr
PULUMI_STACK_CI_NAME: ci
# ── Secrets ────────────────────────────────────────────────────────────────
# Only one secret needs to be set in GitLab CI/CD settings:
# CICD_SECRET_PASSPHRASE: "$CICD_SECRET_PASSPHRASE" (GPG passphrase to decrypt .env.gpg)
# ⚠️ CICD_SECRET_PASSPHRASE MUST be set as a "Protected variable" in GitLab so it is
# never exposed to pipelines triggered from forks.
# All other secrets (DATAROBOT_API_TOKEN, PULUMI_ACCESS_TOKEN, LLM keys, etc.)
# are stored in .env.gpg and sourced automatically in before_script.
before_script:
# Decrypt .env.gpg and source all secrets — only CICD_SECRET_PASSPHRASE must be set in GitLab CI/CD settings
- gpg --quiet --batch --yes --decrypt --passphrase="$CICD_SECRET_PASSPHRASE" --output .env .env.gpg
- export $(grep -v '^#' .env | grep -v '^$' | xargs)
- pip install go-task-bin
- task install
- source .venv/bin/activate
stages:
- check
- review
- deploy
- cleanup
# Linting stage - runs on every merge request from the same project (not forks)
lint:
stage: check
script:
- task lint-check
rules:
- if: $CI_MERGE_REQUEST_ID && $CI_PROJECT_ID == $CI_MERGE_REQUEST_SOURCE_PROJECT_ID
# Testing stage - runs on every merge request from the same project (not forks)
test:
stage: check
script:
- task test
rules:
- if: $CI_MERGE_REQUEST_ID && $CI_PROJECT_ID == $CI_MERGE_REQUEST_SOURCE_PROJECT_ID
# Review app deployment - manual trigger for MR validation (same-project MRs only)
review_app:
stage: review
variables:
PULUMI_STACK: ${PULUMI_STACK_REVIEW_NAME}-${CI_MERGE_REQUEST_IID}
script:
# Install Pulumi
- curl -fsSL https://get.pulumi.com | sh
- export PATH="$HOME/.pulumi/bin:$PATH"
# Login to Pulumi backend (DIY backend example using Azure Blob)
- pulumi login --cloud-url "azblob://dr-ai-apps-pulumi"
# Create the stack if it doesn't exist (PULUMI_STACK selects it for all subsequent commands)
- pulumi stack select --create $PULUMI_STACK
# Deploy the stack
- pulumi up --yes
- echo "Deploying review app for $PULUMI_STACK"
# Get stack outputs and format for GitLab comment
- STACK_OUTPUT="<br><br>$(pulumi stack output --shell)"
- STACK_OUTPUT="${STACK_OUTPUT//$'\n'/<br>}"
# Post comment to merge request with deployment info
- |
curl --header "PRIVATE-TOKEN: $GITLAB_API_TOKEN" \
--data "body=Review Deployment: $STACK_OUTPUT" \
"$CI_API_V4_URL/projects/$CI_PROJECT_ID/merge_requests/$CI_MERGE_REQUEST_IID/notes"
rules:
- if: $CI_MERGE_REQUEST_ID && $CI_PROJECT_ID == $CI_MERGE_REQUEST_SOURCE_PROJECT_ID
when: manual
# Cleanup review app - manual trigger to destroy resources
destroy_review_app:
stage: cleanup
variables:
PULUMI_STACK: ${PULUMI_STACK_REVIEW_NAME}-${CI_MERGE_REQUEST_IID}
script:
- curl -fsSL https://get.pulumi.com | sh
- export PATH="$HOME/.pulumi/bin:$PATH"
- pulumi login --cloud-url "azblob://dr-ai-apps-pulumi"
# Destroy the stack (PULUMI_STACK identifies which stack to target)
- pulumi destroy --yes
# Remove the stack from Pulumi backend
- pulumi stack rm --yes
- echo "Destroyed $PULUMI_STACK stack"
rules:
- if: $CI_MERGE_REQUEST_ID && $CI_PROJECT_ID == $CI_MERGE_REQUEST_SOURCE_PROJECT_ID
when: manual
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
when: manual
needs:
- job: review_app
optional: true
# Continuous delivery - automatic deployment on merge to default branch
deploy_ci:
stage: deploy
variables:
PULUMI_STACK: $PULUMI_STACK_CI_NAME
script:
- curl -fsSL https://get.pulumi.com | sh
- export PATH="$HOME/.pulumi/bin:$PATH"
- pulumi login --cloud-url "azblob://dr-ai-apps-pulumi"
# Select stack, creating it if it doesn't exist yet
- pulumi stack select --create $PULUMI_STACK
- pulumi up --yes
- echo "Deployed $PULUMI_STACK stack"
rules:
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
when: on_success
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |