Rovo Agent
Jenkins for Jira adds a Jenkins agent to Rovo. Ask it, in plain language, how the Jenkins builds of a work item are doing, why a build failed, where a work item has been deployed, or whether a version is ready to ship. It can also start Jenkins builds for you, after you confirmed which ones.
Requirements
- Rovo must be enabled on your Atlassian site.
- Jenkins for Jira must be installed, and at least one Jenkins site must be connected and synchronizing builds.
- The agent isn’t available in Atlassian Government Cloud.
Open the agent
- Open Rovo Chat in Jira, for example from a work item.
- Browse the agents and select Jenkins.
- Pick one of the conversation starters, or ask your own question.
When you start the conversation from a work item, you can refer to it as “this work item”. Otherwise, name the work item
key, for example JJI-123.
Skills
The agent picks the skill that fits your question. You don’t need to name it.
| Skill | What you can ask |
|---|---|
| Build status of a work item | Is this work item building green? Did its latest Jenkins builds pass? |
| Find Jenkins jobs | Which jobs build the payment service? Which jobs are linked to this work item? |
| Start Jenkins builds | Rebuild the Jenkins jobs linked to this work item. |
| Triage a failed build | Why did the latest build of this work item fail? Since when is the job failing? |
| Deployments of a work item | Has this work item been deployed to production? |
| Release readiness | Is everything in version 6.11 built and deployed to production? |
What the agent can see
The agent works as you. It only sees the Jenkins jobs, builds and deployments that you can view in Jira:
- You need the View Jenkins Data or View Developer Tools project permission to see the builds of a work item.
- Starting a build needs the Trigger Jenkins Builds project permission, just like the Trigger a Build action.
When the agent finds nothing, it says that it found nothing you can see. That can mean that there is nothing, but also that you aren’t allowed to view it.
What the agent knows
The agent only answers from the build data that the app synchronizes from Jenkins: per build its result, cause, start time, duration, test counts and deployment environments. The app doesn’t keep console logs, the names of failing tests, commits, branches or the node a build ran on, so the agent can’t tell you those. It links to the build in Jenkins instead.
The agent is told never to invent builds, results or links. Like any AI assistant it can still make mistakes, so follow the links to Jenkins before you act on an answer.
Starting builds
The agent only starts a build when you ask for it. It first shows the exact jobs, the work item and the parameters, and waits for your confirmation. See Start Jenkins builds.
Previous: Confluence Macros
Next: Build Status of a Work Item