Configure a Rovo Dev in Jira session
Configure code and environment settings for your Rovo Dev in Jira session.
Code and environment settings apply only to your Rovo Dev in Jira sessions and are saved per user, per repository, for all future sessions with that repository.
Configure code settings
Code settings enable you to define your branch details and how Rovo Dev pushes code changes to your repository.
To configure code settings:
Go to your work item and select Generate code in the Rovo Dev section.
Select a repository, then select Settings () to open the Code settings dialog.
Enter a branch name and source branch. We recommend using work item keys in the branch name so your branch gets linked back to Jira.
Select the required Branch options to let Rovo Dev push changes to a branch, and create a draft pull request on your behalf. Rovo Dev doesn’t merge the draft pull request directly, your team is still in control of reviewing and merging the code Rovo Dev generates.
Select Save.
Configure environment settings
Rovo Dev sessions can run on your repository with no setup, using its default development tools and languages. But you can customize the session’s sandbox environment by installing and setting up your own tools, too.
To configure environment variables:
Select Generate code in the Rovo Dev section of a work item.
Select a repository. Environment settings only become available after you select a repository.
Select Settings () to open code settings.
Select Environment settings.
Customize the session with variables, secrets, and a script to run on session start:
Environment variables: add KEY=VALUE pairs that are exposed as environment variables to the session sandbox, available to the user and all sandbox processes.
Secrets: add KEY=VALUE pairs accessible from the setup script, secrets are encrypted when stored and only available to the setup script by default (they are not exposed to the session sandbox unless they are manually persisted).
Setup script: runs when the session starts and can be used to install tools, configure build tools, etc. If you require a secret to be stored in a specific location, specify it in the setup script.
Was this helpful?