datarobot-app-framework-cicd

You can set up CI/CD for DataRobot templates by copying ready-to-use workflow files into your repository and configuring Pulumi for declarative infrastructure management. This provides end-to-end patterns for automated testing, review deployments, and production delivery.

Yes, the CI/CD workflows support both GitHub Actions and GitLab CI/CD. You can use platform-specific workflows to run tests on pull requests or merge requests, provision isolated review environments, and deploy continuously to a persistent stack.

You manage secrets using GitHub Secrets with an optional GPG-encrypted .env.gpg flow, or GitLab masked variables. This secure credentials handling ensures sensitive deployment data is protected across your CI/CD pipelines.

You can use common Pulumi backends including Pulumi Cloud, Azure Blob, S3, and GCS. This allows you to declaratively manage and update your DataRobot application infrastructure using your preferred storage backend.

The best way to provision isolated review deployments is using the provided Pulumi workflows to create environments per pull request or merge request. This allows you to validate changes safely before merging to your main branch.

Yes, you can run automated linting and tests on every PR or MR to catch issues early. The CI/CD setup provides automated testing workflows that execute checks against your DataRobot application template changes before merging.