Bitbucket Pipes

Ogoron provides public Bitbucket Pipes for running the same setup, generation, execution, healing, and low-level command workflows from Bitbucket Pipelines.

What this gives you

The public pipe set mirrors the Ogoron GitHub Actions workflow shape:

• ogoron/ogoron-setup-pipe — initialize or upgrade Ogoron in a repository and optionally open a pull request
• ogoron/ogoron-generate-pipe — generate unit, API, and UI test artifacts
• ogoron/ogoron-run-pipe — run generated or project tests
• ogoron/ogoron-heal-pipe — run healing workflows for generated or project tests
• ogoron/ogoron-exec-pipe — run explicit Ogoron CLI commands

Required variables

OGORON_KEY

Main Ogoron repository access token used by the CLI inside Bitbucket Pipelines.

Get it in:

• app.ogoron.ai

Store it as a secured Bitbucket repository or workspace variable.

OGORON_LLM_API_KEY

Only needed when your Ogoron access mode uses BYOK.

If your Ogoron access already includes managed model access, this variable is not required.

BITBUCKET_ACCESS_TOKEN

Only needed for pipe flows that create branches or pull requests, such as setup, generate, and heal with CREATE_PR: "true".

The token should allow repository read/write and pull request creation for the target repository.

Image tags

Each pipe has four public tags:

• 5.2.1 — current pinned release image
• latest — currently points to 5.2.1
• 5.2.1-light — smaller image for unit/API-focused jobs that do not need browser tooling
• light — currently points to 5.2.1-light

Use the pinned version tag in production pipelines. Use latest or light only when you intentionally want the moving tag.

Runtime downloads

The default pipe images are designed to run without downloading test tooling during the CI step.

By default:

• NO_DOWNLOADS is true
• the Ogoron CLI is already available in the image
• the full image includes Python UI workspace dependencies, Playwright Chromium, and Allure CLI
• the light image includes the Ogoron CLI but omits the browser/UI reporting toolchain

Keep NO_DOWNLOADS: "true" for reproducible CI runs. Set it to false only when you intentionally override CLI_VERSION or DOWNLOAD_URL.

Example: setup

pipelines:
  custom:
    ogoron-setup:
      - step:
          name: Set up Ogoron
          script:
            - pipe: ogoron/ogoron-setup-pipe:5.2.1
              variables:
                OGORON_KEY: $OGORON_KEY
                OGORON_LLM_API_KEY: $OGORON_LLM_API_KEY
                CREATE_PR: "true"
                BITBUCKET_ACCESS_TOKEN: $BITBUCKET_ACCESS_TOKEN

Example: generate

pipelines:
  pull-requests:
    "**":
      - step:
          name: Generate Ogoron tests
          script:
            - pipe: ogoron/ogoron-generate-pipe:5.2.1
              variables:
                OGORON_KEY: $OGORON_KEY
                OGORON_LLM_API_KEY: $OGORON_LLM_API_KEY
                UNIT: "true"
                API: "true"
                UI: "true"
                SCOPE: "since:HEAD~5"

Example: run

pipelines:
  pull-requests:
    "**":
      - step:
          name: Run Ogoron tests
          script:
            - pipe: ogoron/ogoron-run-pipe:5.2.1
              variables:
                OGORON_KEY: $OGORON_KEY
                UNIT_TESTS: "true"
                UI_TESTS: "true"

Example: low-level exec

pipelines:
  custom:
    ogoron-exec:
      - step:
          name: Run Ogoron CLI commands
          script:
            - pipe: ogoron/ogoron-exec-pipe:5.2.1
              variables:
                OGORON_KEY: $OGORON_KEY
                COMMANDS: |
                  ogoron --version
                  ogoron generate unit-tests --from-diff --git-scope since:HEAD~5

Notes

• Run setup before generation or execution so .ogoron/ configuration exists.
• Missing generated unit or UI test artifacts are skipped with a clear message in the run pipe.
• Use CREATE_PR: "true" only when you want the pipe to push generated changes and open a Bitbucket pull request.
• Use light tags for unit/API-only jobs where browser execution is not needed.