CloudBees field-contributed plugins and solutions

2 minute read

See -community for plugins and CloudBees field-contributed solutions. The assets in these repositories are free to use. You can modify them as needed.

You can share enhancements and fixes via GitHub. You can also offer suggestions in the form of GitHub project “issues” so that CloudBees or others in the GitHub community can address them.

These assets are not officially supported by CloudBees and have not undergone formal testing. CloudBees is not liable for any repercussions of using this software.


EC-Admin is a collection of administrative procedures to help you manage your CloudBees Flow server. These procedures were developed to respond to requests from customers during CloudBees Professional Services engagements.

This repository contains the following modules:

  • System health

  • Look and feel

  • Jobs and workspaces management

  • Plugins

  • Artifact management

  • Object export backup and restore

  • Schedules

  • Semaphore management

  • License logger

  • postp debugger helper

  • Communication

  • Miscellaneous


This repository contains sample projects created with the CloudBees Flow Domain Specific Language (DSL). This DSL is based on the Groovy programming language and is run directly on the CloudBees Flow server JVM. It has full access to the CloudBees Flow API and can be used for authoring CloudBees Flow content (such as procedures, workflow, and pipelines) and for automation.

For more information about CloudBees Flow DSL, see Using the CloudBees Flow DSL.


This is a CloudBees Flow DSL web-based tool for editing and running DSL scripts.

The DSL IDE is a CloudBees Flow plugin.


This is an easy-to-use testing tool for writing specifications and acceptance tests.

  1. Download the CloudBees Flow <solution name>.jar file from the Electric Cloud Community Forums web site. For this example, the solution name is Test.

  2. Save your download to a temporary directory on the system that hosts your CloudBees Flow server.

  3. Unpack the jar file in the temporary directory—the file creates a directory named Test.

    • If Java JDK is installed, use the included jar utility to unpack the .jar file: %jar xf Test.jar

    • For Linux, use any unzip utility, for example: unzip Test.jar

    • For Windows, use Windows Explorer to access the jar contents if you rename the file to

  4. Run the included script in the jar through the ec-perl interpreter (installed in the bin directory). You must have “admin” or equivalent privileges to run the setup script.