DevOps: Overview

The Ossum DevOps process operates as a hub that coordinates the activities you want to perform after commits are received in your Git repositories.

Ossum works with your existing Continuous Integration server, it does not replace it. Instead of needing to configure your CI server to poll your repository to look for changes, Ossum will automate the process of initiating your jobs as soon as commits are received, helping to speed up the feedback loop for your developers. In addition to this, the Ossum DevOps process pulls back the results of your CI jobs and updates the related work items to show the status of those jobs right on your planning board.

Finally, the Ossum DevOps process assists with Merge Requests and your code review process. As new merge requests are created and modified, Ossum can initiate a verification job that could run tests, style checks or just a build, and communicate those results back to the Merge Request to assist in the decision on when the change is ready to be merged.

Sequence Diagram

Diagram

Feature Summary

Once the DevOps feature has been configured in Ossum you benefit from the following features:

  1. Builds will be initiated on your Jenkins server after commits are pushed to your Git repository in Ossum.

  2. Status of the latest build will be shown on story cards related to the build, both on your planning board and when browsing your commit history.

Kanban Board

  1. Merge Requests can initiate jobs on your Jenkins server to verify the merge request, and a thumbs up/down vote will be provided on the merge request based on the success/failure of the job.

Merge Request

  1. More features will be coming soon...
Previous Article
Code: Overview of Ossum Source Code Management

Next Article
DevOps: Configuring Jenkins for Ossum DevOps