Configuring project template build pre-processing properties

The build pre-processing options define agent pools, and repository triggers among other things.

  1. From the IBM® UrbanCode™ Build dashboard, click Template, then click a project template.
  2. Click Build Pre-Processing.
  3. Click Edit.
  4. Type a number of seconds to wait between builds in the Time Period field.

    The quiet period determines the amount of time that must pass after changes are made to the source before another build can begin. The value represents seconds.

  5. Type a number of seconds to wait between merge triggers in the Merge Period field.
    The merge period is the amount of time to wait after a file is added to the source repository before another build can begin. The value represents seconds.
  6. Specify criteria that are used to search for source and dependency changes.

    To use a label, type a property or a property value. To specify a property, use the property syntax, such as ${p:my.property}. To specify a property value, type the value, such as my property value.

    To use a stamp, enter the stamp value or a pattern. Patterns can contain '?' for a single character, and '*' any sequence of characters. For example, 1.? matches 1.2 but not 1.2.0; 1.* matches both 1.2 and 1.2.0.

    Use the plus icon to enter additional values. Use the drag-and-drop icon to reorder values. If multiple values are specified, they are searched in order, top to bottom.

  7. Specify an agent pool:
    1. To pick a specific pool, click Agent Pool Selection, then select the pool from the list.
      The job runs on the first available agent in the selected pool.
    2. To select the pool by property, click Agent Pool Property, then type the property, such as ${p:my.property}.
  8. To clean the working directory before processing begins, select Yes for the Should Claenup option; otherwise, select No.
  9. To use a precondition script for steps using this template, select the script from the Step Pre-Condition Script list.
    For information about step precondition scripts, see Creating step-precondition scripts
  10. Click Save.