Chapter 8. Performing advanced builds

• Limit resource use by specifying resource limits in the default container limits of a project.

• Limit resource use by specifying resource limits as part of the build configuration.

  • In the following example, each of the resources, cpu, and memory parameters are optional:

    apiVersion: "v1"
    kind: "BuildConfig"
    metadata:
      name: "sample-build"
    spec:
      resources:
        limits:
          cpu: "100m" 

    1

    
          memory: "256Mi" 

    2

    Copy to Clipboard Toggle word wrap

    1

    cpu is in CPU units: 100m represents 0.1 CPU units (100 * 1e-3).

    2

    memory is in bytes: 256Mi represents 268435456 bytes (256 * 2 ^ 20).

    However, if a quota has been defined for your project, one of the following two items is required:

    • A resources section set with an explicit requests:

      resources:
        requests: 

      1

      
          cpu: "100m"
          memory: "256Mi"

      Copy to Clipboard Toggle word wrap

      1

      The requests object contains the list of resources that correspond to the list of resources in the quota.

    • A limit range defined in your project, where the defaults from the LimitRange object apply to pods created during the build process.

      Otherwise, build pod creation will fail, citing a failure to satisfy quota.

Procedure

• To set maximum duration, specify completionDeadlineSeconds in your BuildConfig. The following example shows the part of a BuildConfig specifying completionDeadlineSeconds field for 30 minutes:

  spec:
    completionDeadlineSeconds: 1800

  Copy to Clipboard Toggle word wrap

Procedure

• Assign builds to run on specific nodes by assigning labels in the nodeSelector field of the BuildConfig, for example:

  apiVersion: "v1"
  kind: "BuildConfig"
  metadata:
    name: "sample-build"
  spec:
    nodeSelector:

  1

  
      key1: value1
      key2: value2

  Copy to Clipboard Toggle word wrap

  1

  Builds associated with this build configuration will run only on nodes with the key1=value2 and key2=value2 labels.

• Changing Parallel to Serial or SerialLatestOnly and triggering a new build from this configuration causes the new build to wait until all parallel builds complete as the serial build can only run alone.
• Changing Serial to SerialLatestOnly and triggering a new build causes cancellation of all existing builds in queue, except the currently running build and the most recently created build. The newest build runs next.