CI/CD integration
Outerbounds integrates seamlessly to CI/CD systems. Read this comprehensive blog post about the topic.
GitOps for Outerbounds
The following diagram illustrates a typical CI/CD pattern:
The user experiments and prototypes code on a cloud workstation or locally on a laptop. Crucially, the user is able to test their code at scale quickly and autonomously in to the Outerbounds cluster.
When the code seems to work adequately, they commit it and open a pull request. They authenticate with the CI/CD system using their personal credentials.
The CI/CD system, e.g. GitHub Actions, CircleCI can be configured to launch a test suite automatically when a pull request is opened. The CI/CD system submits workloads to Outerbounds authenticating as a machine user.
After tests pass, a human reviewer reviews the pull request. The reviewer may tag the pull request as approved and a corresponding Metaflow tag can be applied to tests as well, signalling a successful PR.
After the PR has been approved, the CI/CD system deploys the flow either as a new production version or as a ew
@project
variant, running concurrently with the production version so its performance can be evaluated live.
Using Outerbounds with GitHub Actions
This video and the accompaniying repository demonstrates the key workflows in practice:
Follow instructions in this repository to set up OBP work with GitHub Actions. You can apply the same instructions to other CI/CD systems with minor modifications.
Don't hesitate to contact support on Slack if you need help setting up GitOps effectively in your environment.