Jenkins

Add a pipeline stage that installs the DevTools CLI, runs your YAML flows, and publishes JUnit results. Works in classic and declarative pipelines.

Required env vars

Depends on your flows. Common examples:

LOGIN_EMAIL, LOGIN_PASSWORD
API keys or base URLs via Jenkins credentials/bindings

How to run it

Add a stage to your Jenkinsfile:

stage('API Tests') {
  steps {
    sh 'curl -fsSL https://sh.dev.tools/install.sh | bash'
    sh 'devtools flow run --report junit:test-results.xml tests.yaml'
  }
}

TODO:

Screenshot of Jenkins stage view with test results.
Clip of console output showing devtools and JUnit publish.

pipeline {
  agent any
  stages {
    stage('API Tests') {
      steps {
        sh 'curl -fsSL https://sh.dev.tools/install.sh | bash'
        sh 'devtools flow run --report junit:test-results.xml tests.yaml'
      }
    }
  }
}

What to change

Path to your YAML flows file (tests.yaml).
Declarative vs scripted pipeline syntax.
Publish JUnit results as a post step or via plugin.

Common variations

Parallel stages per microservice.
Credentials binding for secrets.
Scheduled nightly/regression jobs.

Links