Overview

What is a Plugin

A plugin provides an ability to extend CloudBees CD’s capabilities by providing Integrations with CD and where necessary with Third Party Software products with the goal of addressing use cases ranging from Code Checkin all the way to the Release of an Application. These are some examples:

• ECSCM-Git plugin extends CD to perform code checkouts, preflight build, and continuous integration with any Git compliant SCM (for example GitHub, GitLab etc.,) .
• EC-Artifactory plugin extends CD to Publish and Retrieve Artifacts from JFrog Artifactory.
• EC-Weblogic plugin extends CD to Deploy Web Applications to the Weblogic Application Server.
• EC-EC2 plugin extends CD to spin Compute Resources in AWS.
• EC-Jenkins plugin extends CD to Run and Monitor Build Jobs on a Jenkins CI server
• EC-Jira plugin extends CD to manage issues in the Atlassian JIRA Issue Management System.
• EC-Admin plugin extends CD by providing a collection of administrative procedures that helps in managing the CD Server.

Plugin Types

There are two types of plugins:

• Plugins that extend CloudBees CD as mentioned above and are installed on the CD Platform. These plugins are informally referred to as CD Plugins.
• Plugins that make CloudBees CD features available in other platforms (for example Jenkins, TFS etc.,). These plugins are developed using the specific platform’s native plugin infrastructure and typically use CD Rest APIs for integrating with CD. These plugins that run natively on a Thirdparty platform using its infrastrcture are informally referred to as Native plugins .