Rovo Dev code review in Bitbucket Cloud
Rovo Dev, Atlassian's AI agent, can review Bitbucket Cloud pull requests and leave comments on quality, security and performance issues. It is turned on twice: for the workspace, then for each repository. Below is how, from Atlassian's pages Activate code reviews in your repository, Trigger a code review and Troubleshoot Rovo Dev code reviews. Atlassian's pages name Bitbucket and GitHub; they do not mention Bitbucket Data Center.
Turn it on
It needs Rovo Dev on your Atlassian site, and Bitbucket connected to Jira. Then:
- The workspace (a workspace admin): Settings → Workspace settings → Atlassian integrations → Rovo Dev. Under Rovo Dev credits, select the Jira site, then turn on Use Rovo Dev in this workspace.
- A repository (needs Rovo Dev Admin permissions): Repository settings → Rovo Dev code review, and turn on AI code reviews in this repository. Or, on the workspace's Rovo Dev page, Activate code review for all repositories, or Activate for all eligible repositories: those where code review was never turned on and you are a repository admin.
When it runs
- Only when pull request is created (the default): one review when the pull request is opened, none for later commits.
- When pull request is created and on each commit: a review for every new commit too.
- Don't review automatically: only when the author starts one.
To start a review by hand, the pull request's author selects Review code in the Rovo Dev section of the pull request's Overview tab, waits a few minutes and refreshes the page. Only the author can. Each commit is reviewed once, so there is no manual review on a repository set to review on each commit. (Atlassian's activation page says instead that the author comments @atlassian /review; its page on triggering reviews gives that comment for GitHub only.)
Whose credits it uses
A review uses Rovo Dev credits from the pull request author's allocation, on the Jira site chosen under Rovo Dev credits. To use fewer, let it run only when pull requests are created, or only by hand.
Why it leaves no comments
- Nothing to say. If Rovo Dev has no feedback, it leaves no comment.
- Too large. A pull request with more than 9,000 lines of changes, or a repository larger than 20 GB, may get no comments, or one saying the pull request is too large. Split the pull request.
- No credit site. A workspace that came from the Rovo Dev Agents beta may have no site under Rovo Dev credits: select one and run the review again.
- Rate limit. Rovo Dev reviews up to about 10 pull requests a minute in a workspace; wait a few minutes.
- Out of credits. Wait for the usage to reset, or ask an admin to raise the limit. A billing or subscription problem stops it too.
- A system error. Wait a few minutes and try again; if it keeps failing, a repository admin turns code review off and on.
With the Standard plan
Two parts need the pull request author to be on a Rovo Dev Standard plan, on the Jira site connected to the workspace:
- Acceptance criteria: if the pull request is linked to a Jira work item, Rovo Dev checks the code against its requirements or acceptance criteria.
- Custom instructions: a file
.rovodev/.review-agent.mdat the repository's root, with the team's standards and what to ignore.
Rovo Dev's comments in IntelliJ IDEA
Pull Request Inbox for Bitbucket, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, has no AI of its own. It shows Bitbucket Cloud and Data Center pull requests in the IDE with all their comment threads, so Rovo Dev's comments are there with the people's, in the thread list and in the diff's gutter. In any comment, a code suggestion says which lines it replaces. The review inbox and reading comments are free; commenting, replying, resolving, approving and merging are Pro (US$1.50 a month, with a 30-day trial).
Get it on JetBrains Marketplace
Bitbucket, Jira, Rovo and Atlassian are trademarks of Atlassian; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with or endorsed by Atlassian or JetBrains.
More: code suggestions · resolving comments · Bitbucket pull request plugins for IntelliJ IDEA, compared · 日本語