← ClaudeAtlas

datarobot-app-framework-cicdlisted

Guidance 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.
datarobot-oss/datarobot-agent-skills · ★ 18 · DevOps & Infrastructure · score 81
Install: claude install-skill datarobot-oss/datarobot-agent-skills
# DataRobot Application Templates CI/CD Skill This skill provides comprehensive guidance for setting up production-grade CI/CD pipelines for DataRobot application templates, including automated testing, review deployments, and continuous delivery. ## Quick Start **Default behavior:** When a user asks to "set up CI/CD" without specifying a platform or backend, always use the [Simple Path](#simple-path-pulumi-cloud--github-secrets) below — three workflow files, two GitHub Secrets, done. Do not create `infra/scripts/`, do not add CI/CD tasks to `infra/Taskfile.yaml`, do not involve GPG encryption unless the user explicitly asks for it. Only deviate from the simple path when the user specifies: - A specific Pulumi state backend (Azure Blob, S3, GCS) → use `scripts/` and see [Implementation Pattern](#implementation-pattern) - GitLab CI/CD → see [GitLab CI/CD Configuration](#gitlab-cicd-configuration) - Many secrets to manage → consider GPG approach in `scripts/` ## Simple Path: Pulumi Cloud + GitHub Secrets For most data scientists and AI engineers, this is all you need. No GPG encryption, no cloud storage account, no extra scripts. **What to create in the user's repository:** 1. Copy the three workflow files to `.github/workflows/`: | Source | Destination | Trigger | |--------|-------------|---------| | `examples/github-cd-pulumi-cloud.yml` | `.github/workflows/cd.yml` | Automatic — every merge to `main` | | `examples/github-deploy-pulumi-cloud.yml` | `.githu