Skip to main content
The IronBee GitLab component can run the verification in two places:
  • Platform mode: on IronBee. The console calls this On IronBee.
  • Local mode: on your GitLab runner. The console calls this On your GitLab 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 merge request by IronBee itself. The verification_mode input picks the mode: auto (the default), platform or local.

Compare the two modes


How auto decides

With verification_mode: auto, the component decides from two things it can check without calling IronBee: the project’s visibility, and whether an Anthropic credential is set. The first line of the plan in the job log names the mode and the reason.
If your project is private or internal and its group is connected to IronBee, set verification_mode: platform explicitly. Otherwise auto runs on your runner whenever an Anthropic credential is set.
A private project whose group 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.

Inputs that apply to one mode

The component warns in the job log when you set an input 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 input.

What’s next?

How it works

The run from the plan to the report.

GitLab

Connect your GitLab group so IronBee can read private projects.