Here's a description of the automation I'm working on:
1. trigger on commit created (with various conditions to only grab certain commits)
2. prompt a custom Rovo agent I created to write an analysis of a Java test class given the bitbucket link to the test class
3. publish a confluence page and put the Rovo-generated analysis in the body of the page along with the link to the file on bitbucket
4. transition the corresponding ticket to Done in Jira
Here's my issue: My custom Rovo agent is successfully able to analyze the test class if I go to Confluence, prompt the agent with the Bitbucket link, and then click to insert the AI response into the Confluence page. However, when the custom agent is given the exact prompt with the same link as a step in the automation rather than manually, the agent's response is something like this:
"Unable to access the provided Bitbucket link due to authorization restrictions. Please ensure the link is publicly accessible or provide the source code directly for analysis."
In the automation, I have the Rovo agent connected to my user, so I would think it should have the same permissions both inside and outside the automation. Is there something I'm missing that would make this work as I want it to?
EDIT: It turns out the AI agent actually doesn't have access in either place. The only difference was the responses created in the automation were errors, while the responses in the manual prompting were hallucinations/guesses. Still, is there a way I can give my AI agent access to read bitbucket files via a link?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.