=========== Overview =========== What is a Plugin ================ A plugin provides an ability to extend CloudBees Flow's capabilities by providing Integrations with Flow 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 Flow to perform code checkouts, preflight build, and continuous integration with any Git compliant SCM (for example GitHub, GitLab etc.,) . * EC-Artifactory plugin extends Flow to Publish and Retrieve Artifacts from JFrog Artifactory. * EC-Weblogic plugin extends Flow to Deploy Web Applications to the Weblogic Application Server. * EC-EC2 plugin extends Flow to spin Compute Resources in AWS. * EC-Jenkins plugin extends Flow to Run and Monitor Build Jobs on a Jenkins CI server * EC-Jira plugin extends Flow to manage issues in the Atlassian JIRA Issue Management System. * EC-Admin plugin extends Flow by providing a collection of administrative procedures that helps in managing the Flow Server. Plugin Types ============ There are two types of plugins: * Plugins that extend CloudBees Flow as mentioned above and are installed on the Flow Platform. These plugins are informally referred to as **Flow Plugins**. * Plugins that make CloudBees Flow 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 Flow Rest APIs for integrating with Flow. These plugins that run natively on a Thirdparty platform using its infrastrcture are informally referred to as **Native plugins** .