Automating Your AI Services: Integrating cli.do with Your CI/CD Pipeline

In the rapidly evolving world of AI, speed and reliability are paramount. As development teams build sophisticated agentic workflows to automate complex business processes, they face a critical challenge: how to deploy and manage these services efficiently and consistently. Manual deployments are slow, error-prone, and simply don't scale. The solution? Treating your AI services like any other critical piece of software—by embracing automation and the principles of "Business as Code."

This is where cli.do, our powerful command-line interface, transforms your development lifecycle. It bridges the gap between building intelligent agents and deploying them robustly, allowing you to integrate the full power of agentic workflows directly into your CI/CD pipeline.

Why Automate Agentic Workflows with a CLI?

In modern software development, Continuous Integration and Continuous Deployment (CI/CD) are standard practice. They enable teams to ship features faster and with greater confidence. Your AI-powered services deserve the same rigorous, automated treatment.

Integrating a CLI into your CI/CD pipeline offers several key advantages:

• Speed: Automatically deploy new versions of your workflows on every push to your main branch.
• Consistency: Eliminate "it works on my machine" problems by using a standardized deployment script for all environments.
• Reliability: Reduce the risk of human error during complex deployment procedures.
• Scalability: Manage hundreds of agentic workflows as easily as you manage one.

Meet cli.do: Your Business Logic, Now in Your Terminal

The .do CLI is a first-class developer tool designed for automation. It brings the full power of the .do platform to the comfort of your terminal, turning complex orchestrations into simple, scriptable commands.

Instead of navigating a UI, you can build, test, and deploy your "Services-as-Software" with intuitive commands.

// Example: Deploying a new agentic workflow from your terminal

// Step 1: Login to your .do account
$ do login

// Step 2: Navigate to your workflow directory and deploy
$ cd /path/to/my-agent-workflow
$ do workflow deploy . --name="customer-onboarding-v2"

// Output:
// ✓ Authenticating...
// ✓ Packaging workflow files...
// ✓ Uploading package (1.2MB)...
// ✓ Deploying agent 'customer-onboarding-v2'...
// ✓ Deployment successful!
//
// API Endpoint: https://api.do/workflows/customer-onboarding-v2
// Status:       Active

Because cli.do is built for scripting, it's the perfect fit for any CI/CD platform, including GitHub Actions, GitLab CI, or Jenkins.

A Practical Guide: Integrating cli.do with GitHub Actions

Let's walk through how to set up a complete CI/CD pipeline using GitHub Actions to automatically deploy your agentic workflow whenever you merge changes to your main branch.

Step 1: Set Up Authentication

Your CI/CD pipeline needs to authenticate with the .do platform securely. We'll use a .do API token and store it as a repository secret in GitHub.

1. Generate an API token from your .do account dashboard.
2. In your GitHub repository, go to Settings > Secrets and variables > Actions.
3. Click New repository secret.
4. Name the secret DO_API_TOKEN and paste your token as the value.

Step 2: Create the GitHub Actions Workflow File

In your repository, create a new file at .github/workflows/deploy.yml. This file will define the automation steps.

# .github/workflows/deploy.yml

name: Deploy Agentic Workflow

# Trigger the workflow on pushes to the main branch
on:
  push:
    branches:
      - main

jobs:
  deploy:
    runs-on: ubuntu-latest

    steps:
      # 1. Check out the repository code
      - name: Checkout code
        uses: actions/checkout@v4

      # 2. Set up Node.js (required to install the CLI via npm)
      - name: Setup Node.js
        uses: actions/setup-node@v4
        with:
          node-version: '20'

      # 3. Install the .do CLI
      - name: Install .do CLI
        run: npm install -g @do/cli

      # 4. Authenticate using the stored secret
      - name: Login to .do
        run: do login --token ${{ secrets.DO_API_TOKEN }}

      # 5. Deploy the agentic workflow
      - name: Deploy Workflow
        run: do workflow deploy . --name "production-workflow"

Breaking Down the Workflow

• on: push: branches: [ main ]: This tells GitHub to run the job every time code is pushed to the main branch.
• uses: actions/checkout@v4: This standard action checks out your repository's code into the runner environment.
• npm install -g @do/cli: This command installs our command line tool.
• do login --token ${{ secrets.DO_API_TOKEN }}: This is the key to automation. The CLI ahthenticates non-interactively using the secure token we stored earlier.
• do workflow deploy . --name "production-workflow": This is the magic command. It takes the workflow definition from your current directory, packages it, and deploys it to the .do platform under the name "production-workflow," overwriting the previous version.

Beyond Deployment: Full Lifecycle Management

The cli.do tool isn't just for deployment. It provides a comprehensive set of commands to manage the entire lifecycle of your agentic workflows, all from a scriptable interface. You can extend your CI/CD pipeline to:

• Manage Environments: Use do env set to configure different API keys for staging and production.
• Run Integration Tests: After deployment, trigger a workflow run with do workflow run and validate the output.
• Monitor Health: Check the status and logs of a deployed workflow to ensure it's operating correctly.
• Version Control: Easily roll back to a previous version if a deployment introduces a bug.

By integrating these capabilities, you can build a truly robust, end-to-end automation pipeline for your most critical business logic.

Ready to stop deploying manually and start shipping with confidence? Install the .do CLI and bring the power of CI/CD to your agentic workflows today.