GitLab integration

GitLab Integration

Connect a GitLab group once and every merge request in the repositories you pick gets reviewed. Add the IronBee GitLab component and each one is verified against your running app, with the verdict on the merge request itself.

Connect GitLab. Every merge request gets reviewed and verified.

  1. A merge request opensOr gets a push. IronBee picks it up on its own, with no one asking.
  2. Reviewed on its linesCode review reads the change with your team's rules and memories, and opens a thread on each finding with a suggestion.
  3. Verified in a real browserThe GitLab component drives the change against your real backend, on IronBee or on your own runner.
  4. Both on the merge requestThe review and the verification each post their findings, with a pipeline status where IronBee writes one. The evidence is in the Console.

Connect the group once. From then on every merge request in the repositories you pick is reviewed, the GitLab component verifies it in your pipeline, and the evidence lives in the Console.

Code review

A review on the lines of the change

IronBee posts a review note with an inline thread on each finding and a GitLab suggestion, keeps a summary note on the merge request, and sets the IronBee review pipeline status where it writes one.

Let customers download their invoices !317invoice-pdf into mainChanges
src/main/java/app/billing/InvoiceController.java+21−0
25 }
26
27 @GetMapping("/invoices/{id}/pdf")
28 public ResponseEntity<byte[]> download(@PathVariable long id, Principal user) {
29 Invoice invoice = invoices.findById(id).orElseThrow();
ironbee-aiBotreviewed yesterday
CriticalSecurity

Any signed-in customer can download any other customer's invoice: it is looked up by its id alone, never by its owner.

Happens when: a customer changes the number in /invoices/1042/pdf to another one.

Suggested change
Invoice invoice = invoices.findById(id).orElseThrow();
Invoice invoice = invoices.findByIdAndOwner(id, user.getName()).orElseThrow();
Apply suggestion

Rule tenant-isolation a customer only ever reads their own records.

30 return ResponseEntity.ok(pdf.render(invoice));
31 }
IronBee review2 findings · 1 critical · 1 lowfailed
Verification

The whole run, on the merge request

With the GitLab component, the run lands in the same merge request: what the agent did, what it found, and where it came from, as a summary note and inline comments.

IronBee VerificationVerification failed · 2 findings3m 41sfailed
ironbee-aiBotcommented yesterday
Open in IronBee

IronBee Verification

Verification failed1 critical · 1 medium

SeverityFindingWhere
CriticalSigned in as a second customer, the first customer's invoice downloadedInvoiceController.java:29
MediumAn invoice id that does not exist ends on a 500 error page, not a 404InvoiceController.java:29
Checks2 passed · 2 failed
  • Signed in as a customer and downloaded their own invoice
  • Signed in as another customer and opened the first one's invoice link
  • Opened an invoice id that does not exist
  • Signed out and opened an invoice link: sent to sign in
Summary
Important files changed

View the full verification →Used 3 IronBee credits.

Access

A service account, never your name

IronBee works in the group through an account of its own, on the repositories you pick. The token GitLab gave for your account is revoked as soon as the group is connected.

01

Its own service account

IronBee creates a service account in the group, a Maintainer that uses no seat. Reviews, replies and statuses are posted under it.

02

Read-only where your code runs

Code is checked out by an IronBee reader account with the Reporter role, and each job's token is revoked when the job ends.

03

Merges held only when you ask

IronBee's statuses join the merge request's pipeline. On a project with Pipelines must succeed, they hold a merge only once Block merges is turned on.

GitLab FAQ

Reviewing and verifying merge requests, answered.

How the GitLab connection and the IronBee GitLab component review and verify every merge request.

Connect a top-level group on gitlab.com from the IronBee Console and pick its repositories. IronBee then reviews every merge request in them: a review note, an inline thread on each finding with a suggested fix, a summary note and the IronBee review pipeline status. Mention @ironbee-ai on a merge request to ask for a review.

Now generally available

Ready to ship
AI-generated code with confidence?

Create your account and start verifying what your agents ship. Catch regressions before they reach production.

No credit card required.