Welcome
Extending Product Functions
You can create your own plug-ins to extend the product’s capabilities.
Example plug-in
A plug-in consists of one or more steps. A step represents a unit of functionality that a user can configure and combine with other steps into a process. Creating a plug-in consists of defining its individual steps and then grouping them for presentation in Build.

DevOps Loop:Build
Build offers the capability to build applications, manage continuous integration workflows, and store build artifacts.
Overview
Tutorials
Administering
Users with the correct permissions can configure security, create users, configure integrations, and create notifications and announcements among other things.
Creating and Managing Projects
Projects run builds, manage dependencies with third-party tools, and can be used for administrative, operational, and system maintenance.
Creating Jobs and Processes
Jobs are the core building blocks of Build. Process definitions assemble jobs into the basic unit of automation. A process definition determines how, when, and where jobs run.
Managing Project Templates
Project templates are reusable plans that map build processes.
Monitoring and Reporting
With the monitoring tools you can review current and historical activity and save your filter conditions for future use. You can create charts and reports from most database tables.
Extending Product Functions
You can create your own plug-ins to extend the product’s capabilities.
- Plug-ins
  Build plug-ins provide tools for creating workflows and integrating with external tools.
- Example plug-in
  A plug-in consists of one or more steps. A step represents a unit of functionality that a user can configure and combine with other steps into a process. Creating a plug-in consists of defining its individual steps and then grouping them for presentation in Build.
  - Step properties
    In the context of plug-ins and steps, properties are values that the step's command uses. Step properties are defined with the property element.
  - Step commands
    The step's command element specifies the scripting tool that runs the step and identifies the file that contains the actual script.
  - create_file.groovy
    The create_file.groovy file contains the Groovy script that runs the step's command.
- Build Scripting
  The scripting API describes the various types of supported scripts.
- Properties in Build
  Properties can be set for many different things, including projects, build configurations, process configurations, build requests, and the server. You can also set and retrieve agent properties.
- REST API reference
  The Build server has a REST interface, which you can use to automate tasks on the server.

Example plug-in

A plug-in consists of one or more steps. A step represents a unit of functionality that a user can configure and combine with other steps into a process. Creating a plug-in consists of defining its individual steps and then grouping them for presentation in Build.

Plug-in steps are run by an agent that is installed in the target environment. This means that plug-ins can be written in any scripting language provided that the agent can access the required scripting tools on the host.

The mechanics of plug-ins are covered by examining a plug-in step in detail. The example plug-in is Shell, which contains several steps that are related to shell scripts. The Shell plug-in comes with Build.

Each plug-in step is an individually configurable object. In the following illustration, you can see Shell plug-in’s individual steps in the Steps window. The Shell step's label is derived from the description element in the plug-in file.

This example covers the Shell step. The Shell step executes a shell script or batch file that that you supply.

Each step (step-type element has the same structure:

The properties element can contain any number of property child elements. Property values can be supplied at design time or run time.
The post-processing element provides error-handling functions and sets property values that can be used by other steps.
The command element performs the step's function. The function can be defined completely by the element, or be constructed in part or entirely from the step's properties at design time or run time.

The following figure shows how the Shell plug-in property definitions are displayed in the plug-in window.