DevOps: Configure Ossum DevOps Plugin

Configure Ossum DevOps Plugin

The first step is to tell Ossum about your Jenkins server so it will be able to talk to it. Click on the Settings icon on the Ossum top nav and then DevOps.


Ossum will use this information to initiate jobs on your Jenkins server when a commit is pushed or a merge request is created or updated with new changes. You only need to do this once, as the same server configuration will be used for all of your repositories. Ossum does not currently allow you to add multiple Jenkins servers.

Assuming your Jenkins server requires some kind of credentials, use the toggle to tell Ossum whether you are providing a password or a Jenkins API token. Since Ossum has to store and use these credentials with your Jenkins server we recommend using an API token when possible. See:

Configure Git Repository

The last thing to do is configure your Git repository to tell it which job(s) to run. To do this browse your repository in Ossum and click on the Settings icon in the left-hand nav.


There are two places you can optionally specify a job name.

  1. Build CI Settings -- this is the name of job to run after a commit is received. When these jobs run, their results are recorded back and stored on any work item cards that were referenced by the commit(s) that were included in the build.

  2. Merge Request CI Settings -- this is the name of the job to run when a merge request is created or updated with new changes. The results of this job are recorded back on the merge request as a thumbs up or down vote.

Both of these are optional. If no job name is provided, then no job will be initiated when that event occurs. Click the Save option after providing the job name.

Previous Article
DevOps: Configuring Jenkins for Ossum DevOps

Next Article
DevOps: Configuring TeamCity for Ossum DevOps