Hello,
We've just gone through all the steps to get Rovo Dev running for the Bitbucket organisation and specific repos.
However, it seems to hang on `Reviewing pull request` for about 5 minutes before nothing happens.
Then, if I push another commit, I can see it has detected the code changes and prompted with a button to `Review code`, but when I press this it says that `Rovo dev is not activated in the organization.` This doesn't seem to make sense as we can obviously see it is activated in the organization, and my usage is currently at 0 credits.
We've tried to toggle it on and off at the org and repo level, and have double checked the users are in the appropriate Rovo user groups: https://support.atlassian.com/rovo/docs/add-rovo-dev-standard-to-your-site/
Thanks for your support!
Hi @Liam Swift
There are generally 4 things you'll need to check here:
1. Access
2-4. Setting Enablement
There are 3 places to check to make sure RovoDev is enabled as RovoDev must be enabled at each location to ensure bidirectional communication with Bitbucket:
1. Atlassian Admin: You'll need to navigate to https://admin.atlassian.com > Rovo > Rovo Settings > Rovo Dev tab and ensure the Bitbucket & Github slider is switched to enabled
2. JIRA Site Settings: You'll also need to navigate to your JIRA site settings and ensure that the Bitbucket & Github slider is switched to enabled also:
yoursite.atlassian.net/rovodev/site-settings
3. Bitbucket Cloud settings: Finally, you'll need to make sure it's enabled in Bitbucket by navigating to Workspace Settings > Atlassian Integrations > Rovo Dev and ensuring the Use RovoDev in this workspace slider is switched to enabled, from here you'll need to also enable it on either all repositories or only selected repositories
bitbucket.org/yourworkspaceid/workspace/settings/rovo-dev-agents
Please try the above and let me know how it goes.
If you still encounter issues - please let me know your timezone so that I may raise a support ticket on your behalf with the team that operates within your working hours.
Cheers!
- Ben (Bitbucket Cloud Support)
Hi @Liam Swift
I would suggest raising a support ticket directly with Atlassian since prolonged spinner + silent failure usually points to a backend provisioning issue that needs their tooling to clear.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.