When using cloud-native builds, you are essentially distributing build tasks to various build nodes for execution.
These nodes perform build tasks using a specified Docker image as the build environment.

Configuration Method

In the pipeline configuration, you can specify the pipeline.runner.tags property to select different build nodes.
By specifying the pipeline.runner.cpus property, you can configure the maximum number of CPU cores to be used.

The official available tags is as follows:

1. cnb:arch:amd64
   • The cpus can be configured in the range of 1 to 64, with a default value of 8.
   • The CPU with the amd64 architecture.
2. cnb:arch:arm64:v8
   • The cpus can be configured in the range of 1 to 16, with a default value of 8.
   • The CPU with the arm64/v8 architecture.
3. cnb:arch:amd64:gpu
   • The cpus is fixed at 16 with the amd64 architecture.
   • The GPU memory has a maximum of 48GB, operating in shared mode.
4. cnb:arch:amd64:gpu:H20
   • The cpus is fixed at 32 with the amd64 architecture..
   • The GPU memory has a maximum of 96GB, operating in shared mode.
5. cnb:arch:amd64:gpu:L40
   • The cpus is fixed at 16 with the amd64 architecture.
   • The GPU memory has a maximum of 48GB, operating in shared mode.

Example:

main:
  push:
    - runner:
        # execution on amd64
        tags: cnb:arch:amd64
        # use cpus 8
        cpus: 8
      stages:
        - name: uname
          script: uname -a

    - runner:
        # execution on arm64/v8
        tags: cnb:arch:arm64:v8
        # use cpus 8
        cpus: 8
      stages:
        - name: uname
          script: uname -a

$:
  vscode:
    - runner:
        # Start a workspace for remote development with GPU access
        tags: cnb:arch:amd64:gpu
      services:
        - vscode