You can create your own plug-ins to extend the product’s capabilities.
Build offers the capability to build applications, manage continuous integration workflows, and store build artifacts.
Users with the correct permissions can configure security, create users, configure integrations, and create notifications and announcements among other things.
Projects run builds, manage dependencies with third-party tools, and can be used for administrative, operational, and system maintenance.
Jobs are the core building blocks of IBM® DevOps Build (Build) . Process definitions assemble jobs into the basic unit of automation. A process definition determines how, when, and where jobs run.
Project templates are reusable plans that map build processes.
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.
IBM® DevOps Build (Build) plug-ins provide tools for creating workflows and integrating with external tools.
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 IBM® DevOps Build (Build) .
The scripting API describes the various types of supported scripts.
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.
The IBM® DevOps Build (Build) server has a REST interface, which you can use to automate tasks on the server.
