Skip to main content
Version: 24.3

Configuring the integration

  • Configuring Digital.ai Agility
  • Configuring Jenkins
  • Adding support for another Source Code Management system

Step 1. Configuring Digital.ai Agility​

  1. Log into Digital.ai Agility as an administrator.
  2. From the side bar, click the gear icon, and click System under Configuration.
  3. In the Enable Features section, check the Build Integration check box and click Save.
  4. To build a new project, go back to the Admin, select Projects, and the select Pipelines.
  5. Click the Add button, and then enter the following:
    • Name. This is how the build project displays to Digital.ai Agility members.
    • Reference. This is how the build project displays in Jenkins.
    • (Optional) Description. Enter a more details about the build project.
  6. Click Save.
  7. Click on the Projects tab.
  8. Click Edit from the Add Child Project drop-down menu next to the project you want associated with the Pipeline.
  9. Scroll to the Pipelines field and select a Pipeline from the drop-down list.
  10. Click Save to accept the changes and log out of Digital.ai Agility.

Step 2. Configuring Jenkins​

  1. Log into Jenkins as an administrator.
  2. On the Jenkins Dashboard, click Manage Jenkins.
  3. Click Manage Plugins and click Advanced.
  4. Under Upload Plugin, browse to your download location, select the versionone.hpi file, and click Upload.
  5. Restart your Jenkins instance to load the new plugin.
  6. On the Jenkins Dashboard, click Manage Jenkins.
  7. Click Configure System. A new Digital.ai Agility section displays at the end of this page.
  8. Provide your Digital.ai Agility connection parameters.
    Note: if you are connecting to an On-Demand Digital.ai Agility instance, make sure to use the https prefix, not just http.
  9. If you connect to Digital.ai Agility through a proxy, select the Use proxy server check box and provide additional proxy parameters.
    We recommend that you do not change the Reference Field or Comment RegEx fields. Reference Field is the system name of the attribute to search when matching the ID in change comments with work items in Digital.ai Agility. Comment RegEx is used to extract workitem identifiers from the change comments.
  10. Test the connection and save the settings.
  11. Choose the Job you want to publish to Digital.ai Agility. Remember that this job name must be configured in Digital.ai Agility.
  12. Click Configure to configure the workspace.
  13. In the Post-build Actions section, click the VersionOne Notifier check box and click Save.

Adding support for another Source Code Management system​

To add support for new VCS, follow these steps:

  1. Add plugin reference to pom.xml, make sure that this dependency could be successfully resolved.
  2. Add a class wrapping native changeset type. SvnModification or PerforceModification are good examples on how to do it.
    New class must inherit VcsModification interface and provide parameterless public constructor.
  3. Modify VcsModificationWrapperFactory class to support new changeset type.
    It is required to add line similar to classNameMappings.put("jenkins.plugins.perforce.PerforceChangeLogEntry","com.versionone.jenkins.PerforceModification"). String literals are mappings of native changeset log entry classes to our custom wrappers in format supported by Java Reflection, so that instances and class objects could be successfully created. Changesets will be processed as soon as user installs the corresponding plugin and restarts Jenkins server. In fact, our plugin won’t start without its dependencies.