Download link - https://www.kovair.com/adapters/jenkins-blue-ocean-integration-adapter/ The ‘Kovair Jenkins Blue Ocean Integration Adapter’ allows rich data from Jenkins to be monitored and captured to Kovair Omnibus Integration Platform and thereby synchronize with other ALM tools in the system. The primary objective of the integration is to complete pipe line view dynamically from Jenkins. The pipeline view also displays the detail execution status. Moreover, Kovair Adapter allows execution of Pipeline externally.

1. Kovair Jenkins Integration Datasheet
Kovair Jenkins Integration Datasheet
Page1
A Sneak Peak
Kovair Jenkins Adapter integrates
Jenkins with other best-of-breed
ALM tools and provides a
centralized view of the unified
software development.
Benefits
❖ Monitor and track Build, Build
Steps, Pipeline, and Pipeline
Execution from Jenkins into
Kovair ALM.
❖ Execute Deployment from Kovair
ALM central platform.
❖ Provides complete visibility to
view the status of Jenkins Builds
from Kovair ALM or other
integrated tools that are
connected through Omnibus.
❖ Direct navigation to Jenkins
Interface from Kovair ALM to
give the end users a complete
360-degree view.
Features
❖ Synchronization of Build, Steps,
Pipeline, and Pipeline execution
results to Kovair ALM or any
other integrated tool.
❖ Direct Accessibility to Jenkins
Pipeline and Execution from
other integrated tools.
❖ Single interface for all
continuous delivery pipelines
of Jenkins.
OVERVIEW
Jenkins is a popular open source tool for continuous integration and
build automation. Over the time, Jenkins has become the open
source standard for managing the development side of DevOps,
from source code management to delivering code to production.
Jenkins also supporting continuous integration, where code from
individual developers are merged into a deployed project at an
estimated interval and are continuously tested to avoid downstream
problems. CD takes this a step further to ensure that all merged
codes are always in a production-ready state.
Kovair Jenkins Adapter
The ‘Kovair Jenkins Integration Adapter’ allows rich data from
Jenkins to be monitored and captured to Kovair Omnibus
Integration Platform and thereby synchronize with other ALM tools
in the system. The primary objective of the integration is to provide
a consolidated single interface to the end user; for detailing of Build,
Job, Pipeline, and Pipeline execution with traceability.
Single Click Deployment
The integration between Jenkins and Kovair ALM is a deep level
integration. It enables users to avail single click deployment from the
ALM interface. Kovair with its rich integration adapter can extract
pipeline as well as pipeline execution details to Kovair ALM.

2. Kovair Jenkins Integration Datasheet
Kovair Jenkins Integration Datasheet
Page2
System Requirements
❖ Operating Systems: Windows
2008 Server, Windows 2008
Server R2 Server
❖ Databases: SQL Server 2008,
SQL Server 2008 R2,
(Developer,
Standard & Enterprise)
❖ IIS: IIS 7.0 or 7.5
❖ .Net Framework: 4.6 or Higher
Kovair Jenkins Adapter
The integration — between Jenkins, Omnibus, and other
ALM tools — provides a convenient way for managing Build,
Build Steps, and Pipeline. The integration framework
contains two components — an adapter and a plug-in.
Kovair Jenkins Integration Adapter: It is a WCF Service
that exposes Jenkins entities, entity fields, and relations. It
also acts as a connector for triggering a Build in Jenkins from
Kovair Application.
Kovair Listener Plug-In for Jenkins: It is a custom plug-in
that collects Jenkins data and results and then pushes them
in to the adapter. The plug-in needs to be deployed at
Jenkins server.
Entities
Exposed
Events Collected
Actions
Supported
Relations
Supported
❖ Job
❖ Build
❖ Pipeline
View
❖ Pipeline
Execution
❖ Job Modified
❖ Build
Completed
❖ Build to Job
Added
❖ Pipeline View
Added
❖ Pipeline
Execution
Added
❖ Pipeline
Execution
Modified
❖ Pipeline View
Modified
❖ Pipeline View
to pipeline
Execution
Added
❖ Pipeline View
to Job Added
❖ Pipeline View
to Job
Deleted
❖ Execute
Job
❖ Execute
Pipeline
❖ Build to
Job
❖ Pipeline
View to Job
❖ Pipeline
View to
Pipeline
Execution

3. Kovair Jenkins Integration Datasheet
Kovair Jenkins Integration Datasheet
Page3
Why Integrate Jenkins with Kovair?
Trends like agile development, DevOps, and
continuous integration has led to the modern
enterprise’s need for building software
hyper-efficiently.
Kovair ALM along with Kovair Omnibus offers
the capacity of supporting single-click
execution of Jenkins pipeline.
Kovair Omnibus will facilitate an organization
to integrate all major tools in ALM with
Jenkins for monitoring and taking actions in
real time.
Omnibus being an ESB allows one to connect
Jenkins with TFS, Jira, and other ALM for
coding, building, deploying, and tracking
issues.

4. Kovair Jenkins Integration Datasheet
Note: The adapter as developed and offered by Kovair follows the
subject tool’s standard specifications. Any deviations from the tool’s
typical use pattern may not have been anticipated in our off-the-shelf
product. For any customization or special configuration needs, please
contact Kovair Sales - sales@kovair.com
Kovair Software Inc.: Kovair is a California based software product
company specializing in the domain of Application Lifecycle
Management (ALM). Kovair’s focus on integrating third party best-of-
breed ALM tools enables creation of applications in a synchronized
tools environment.
US Office
2410 Camino Ramon, STE 230
San Ramon, CA 94583
Support: 1.408.262.0200 Extn. 2100
Sales: 1.408.262.0200 Extn. 1
Email: sales@kovair.com www.kovair.com
India Office
PTI Building - 6th Floor, DP-9, Sector - V
Salt Lake City, Kolkata - 700091, India
Support: 1.408.262.0200 Extn. 2100
Sales & Marketing: 91-33-4065 7016/17
Email: sales@kovair.com
Jenkins Integration Adapter Offers the Following:
Defect Tracking
Using Kovair Omnibus Integration Platform and relevant adapters, you can integrate Jenkins with defect tracking
systems such as JIRA and reduce the need of maintaining change log.
Improved Product Quality
Bugs that arise when changes are merged with the source control repository are rarely identified because the
problem is not localized. It mainly arises from the interaction between two pieces of work. Often, integration
bugs start infecting the system weeks or months after they were inserted. As a result, it takes a lot of effort to
identify those bugs.
Continuous Integration with Jenkins ensures that a vast majority of integration bugs manifest themselves
immediately and are easy to detect. This greatly reduces the scope of search for the integration bugs. If you
cannot find the bug, you can avoid putting the offending code into the product so that in the worst case you do
not add the feature that contains the bug.