You can create your own plug-ins to extend the product’s capabilities.
The Build server has a REST interface, which you can use to automate tasks on the server.
The following list shows the commands that are available.
Build offers the capability to build applications, manage continuous integration workflows, and store build artifacts.
Build is a continuous integration and build-management system.
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.
A build pipeline defines the automated process that transforms source code into deployable artifacts. It specifies the steps required to compile, test, validate, scan, and package the code.
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.
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.
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 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.
Many different programs can run REST commands. To run the command, you call a method on a REST resource and pass parameters or a request in JSON format.
The way that you authenticate to run REST commands depends on how the server is set up and the tool that you are using to run the commands.
The Build REST API follows a set of conventions to make interacting with it more consistent.
Resources for working with agents.
Return a JSON representation of the summary of all the findings in the source analytic report.
Return a JSON representation of all source analytic reports.
Return a JSON representation of all source analytic summary reports.
Return the details of all the build lives for a project.
Return a JSON representation of all code coverage reports.
Return a JSON representation of all issues.
Return a JSON Array representation of all labels.
Return a JSON representation of all the findings in the source analytic report.
Return a JSON Array representation of all source change sets.
Return a JSON Array representation of all statuses.
Return a JSON representation of all test reports.
Return a JSON representation of the source analytic report.
Return a JSON representation of the source analytic summary report.
Resources for working with build process templates.
Resources for working with process templates.
Resources for working with secondary process templates.
Resources for working with source config templates.
Resources for working with project templates.
