Welcome
Administering
Users with the correct permissions can configure security, create users, configure integrations, and create notifications and announcements among other things.
Project support
Projects represent items that can be built individually for release or distribution.
Managing cleanups
Cleanups are scheduled based on the cleanup policy. The cleanup policy contains settings that determine when build lives, build requests, and miscellaneous jobs are cleaned up.

DevOps Loop: Build
Build offers a robust, template-driven system for managing continuous integration and build processes.
Overview
Tutorials
Administering
Users with the correct permissions can configure security, create users, configure integrations, and create notifications and announcements among other things.
- Integrations
  When you configure integrations, you allow Build to use and manage the objects and artifacts that are produced in external tools such as HCL DevOps Deploy (Deploy).
- Managing scripts
  The script library provides numerous scripts for you to use and modify.
- User notifications
  Build can send information about build results to selected users by email, instant messaging, and other methods.
- Security
  Build provides a flexible team-based, and role-based security model that maps to your organizational structure.
- Project support
  Projects represent items that can be built individually for release or distribution.
  - Creating artifact sets
    Artifact sets are groups of artifacts that are produced by a build.
  - Managing cleanups
    Cleanups are scheduled based on the cleanup policy. The cleanup policy contains settings that determine when build lives, build requests, and miscellaneous jobs are cleaned up.
  - Adding and editing cleanup policy settings
    Use the cleanup settings to determine when build lives, build requests, and miscellaneous jobs are cleaned up.
  - Managing Labels
    Labels are assigned to build lives. Using the Label page, you can create, modify, and delete labels. Deleting a label removes the label from the server.
  - Creating lockable resources
    Lockable resources are resources that can be reserved by other objects, such as agents, when a process runs.
  - Repositories
    Repositories contain the source materials that are used in build processes.
  - Creating schedules
    You can use schedules to determine when certain events, such as builds and backups, occur.
  - Creating statuses
    Statuses represent build conditions, such as success or failure.
- Server management
  Use server settings to manage your server other system-related settings.
- Agents
  Agents are light-weight processes that are installed on hosts and communicate with the Build server.
- Creating scripts to automate administrative tasks
  The Build Client facilitates writing scripts that interact with various REST endpoints in Build to automate tasks such as creating templates, assembling projects, running builds, and various other administrative tasks.
- Accessing development tools
  Use the Tools window to access the Build development tools.
- Installing plug-ins
  You install plug-ins by downloading the installation files and loading them into Build.
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.

Managing cleanups

Cleanups are scheduled based on the cleanup policy. The cleanup policy contains settings that determine when build lives, build requests, and miscellaneous jobs are cleaned up.

About this task

Build life cleanup is determined by cleanup type and retention policy. Each build life is evaluated by its status. A build without a status is evaluated with the All Builds status. If the All Builds type has the Keep Days property or Keep Latest property set to Forever, no builds with this type are be cleaned up. A build life is not cleaned up if either the Keep Days or Keep Latest properties are met.

Procedure

Complete the following steps to schedule a cleanup.

On the left navigational panel, click System > Cleanup.
Click Edit.
Select a schedule from the Schedule list.
Schedules are defined on the Schedules page, see Creating schedules.
Specify a number of days to keep lockable resources in the Days to Keep Lockable Resources field.
This option applies to resources such as working directories. The default value is 30 days. Enter -1 to never clean up lockable resources.
Specify the number of days to keep preflight builds in the Days to Keep Preflight Builds field.
The default value is 30 days. Enter -1 to never clean up lockable resources.
Click Save.
Optional: Create additional cleanup policies.
Click New to create a cleanup policy. See Adding and editing cleanup policy settings for details on cleanup policy settings.
Click Done after you finish.