Skip to main content
The IronBee Pipe can run the verification in two places:
  • Platform mode: on IronBee. The console calls this On IronBee.
  • Local mode: inside the pipe, on your Bitbucket Pipelines runner. The console calls this On your Bitbucket Pipelines runner.
Everything after the verification works the same way in both modes: the verdict, the fix, the commit and the report. Only a run on IronBee can be published on the pull request by IronBee itself. The VERIFICATION_MODE variable picks the mode: auto (the default), platform or local.

Compare the two modes


How auto decides

With VERIFICATION_MODE: auto, the pipe decides from two things it can check without calling IronBee: whether the repository is private, and whether an Anthropic credential is passed. The first line of the plan in the step log names the mode and the reason.
If your repository is private and its workspace is connected to IronBee, set VERIFICATION_MODE: "platform" explicitly. Otherwise auto runs on your runner whenever an Anthropic credential is passed.
A private repository whose workspace isn’t connected can still be verified on IronBee: set IRONBEE_BIND_REPOSITORY: "false" to verify the running application without a checkout of the repository.

Variables that apply to one mode

The pipe warns in the step log when you set a variable that doesn’t apply to the mode it runs in. Platform mode only Local mode only CLAUDE_CODE_CLI_VERSION and the Anthropic credential also apply to the fix step in platform mode. See Configuration for every variable.

What’s next?

How it works

The run from the plan to the report.

Bitbucket

Connect your Bitbucket workspace so IronBee can read private repositories.