/AWS1/CL_BLD=>UPDATEFLEET()
¶
About UpdateFleet¶
Updates a compute fleet.
Method Signature¶
IMPORTING¶
Required arguments:¶
IV_ARN
TYPE /AWS1/BLDNONEMPTYSTRING
/AWS1/BLDNONEMPTYSTRING
¶
The ARN of the compute fleet.
Optional arguments:¶
IV_BASECAPACITY
TYPE /AWS1/BLDFLEETCAPACITY
/AWS1/BLDFLEETCAPACITY
¶
The initial number of machines allocated to the compute fleet, which defines the number of builds that can run in parallel.
IV_ENVIRONMENTTYPE
TYPE /AWS1/BLDENVIRONMENTTYPE
/AWS1/BLDENVIRONMENTTYPE
¶
The environment type of the compute fleet.
The environment type
ARM_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), Asia Pacific (Mumbai), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), EU (Frankfurt), and South America (São Paulo).The environment type
ARM_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai).The environment type
LINUX_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai).The environment type
LINUX_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai).The environment type
LINUX_GPU_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), and Asia Pacific (Sydney).The environment type
MAC_ARM
is available for Medium fleets only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), and EU (Frankfurt)The environment type
MAC_ARM
is available for Large fleets only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), and Asia Pacific (Sydney).The environment type
WINDOWS_EC2
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Tokyo), Asia Pacific (Singapore), Asia Pacific (Sydney), South America (São Paulo), and Asia Pacific (Mumbai).The environment type
WINDOWS_SERVER_2019_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Asia Pacific (Mumbai) and EU (Ireland).The environment type
WINDOWS_SERVER_2022_CONTAINER
is available only in regions US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), EU (Frankfurt), Asia Pacific (Sydney), Asia Pacific (Singapore), Asia Pacific (Tokyo), South America (São Paulo) and Asia Pacific (Mumbai).For more information, see Build environment compute types in the CodeBuild user guide.
IV_COMPUTETYPE
TYPE /AWS1/BLDCOMPUTETYPE
/AWS1/BLDCOMPUTETYPE
¶
Information about the compute resources the compute fleet uses. Available values include:
ATTRIBUTE_BASED_COMPUTE
: Specify the amount of vCPUs, memory, disk space, and the type of machine.If you use
ATTRIBUTE_BASED_COMPUTE
, you must define your attributes by usingcomputeConfiguration
. CodeBuild will select the cheapest instance that satisfies your specified attributes. For more information, see Reserved capacity environment types in the CodeBuild User Guide.
BUILD_GENERAL1_SMALL
: Use up to 4 GiB memory and 2 vCPUs for builds.
BUILD_GENERAL1_MEDIUM
: Use up to 8 GiB memory and 4 vCPUs for builds.
BUILD_GENERAL1_LARGE
: Use up to 16 GiB memory and 8 vCPUs for builds, depending on your environment type.
BUILD_GENERAL1_XLARGE
: Use up to 72 GiB memory and 36 vCPUs for builds, depending on your environment type.
BUILD_GENERAL1_2XLARGE
: Use up to 144 GiB memory, 72 vCPUs, and 824 GB of SSD storage for builds. This compute type supports Docker images up to 100 GB uncompressed.
BUILD_LAMBDA_1GB
: Use up to 1 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
BUILD_LAMBDA_2GB
: Use up to 2 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
BUILD_LAMBDA_4GB
: Use up to 4 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
BUILD_LAMBDA_8GB
: Use up to 8 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.
BUILD_LAMBDA_10GB
: Use up to 10 GiB memory for builds. Only available for environment typeLINUX_LAMBDA_CONTAINER
andARM_LAMBDA_CONTAINER
.If you use
BUILD_GENERAL1_SMALL
:
For environment type
LINUX_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs for builds.For environment type
LINUX_GPU_CONTAINER
, you can use up to 16 GiB memory, 4 vCPUs, and 1 NVIDIA A10G Tensor Core GPU for builds.For environment type
ARM_CONTAINER
, you can use up to 4 GiB memory and 2 vCPUs on ARM-based processors for builds.If you use
BUILD_GENERAL1_LARGE
:
For environment type
LINUX_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs for builds.For environment type
LINUX_GPU_CONTAINER
, you can use up to 255 GiB memory, 32 vCPUs, and 4 NVIDIA Tesla V100 GPUs for builds.For environment type
ARM_CONTAINER
, you can use up to 16 GiB memory and 8 vCPUs on ARM-based processors for builds.For more information, see On-demand environment types in the CodeBuild User Guide.
IO_COMPUTECONFIGURATION
TYPE REF TO /AWS1/CL_BLDCOMPUTECONF
/AWS1/CL_BLDCOMPUTECONF
¶
The compute configuration of the compute fleet. This is only required if
computeType
is set toATTRIBUTE_BASED_COMPUTE
.
IO_SCALINGCONFIGURATION
TYPE REF TO /AWS1/CL_BLDSCALINGCONFINPUT
/AWS1/CL_BLDSCALINGCONFINPUT
¶
The scaling configuration of the compute fleet.
IV_OVERFLOWBEHAVIOR
TYPE /AWS1/BLDFLEETOVERFLOWBEHAVIOR
/AWS1/BLDFLEETOVERFLOWBEHAVIOR
¶
The compute fleet overflow behavior.
For overflow behavior
QUEUE
, your overflow builds need to wait on the existing fleet instance to become available.For overflow behavior
ON_DEMAND
, your overflow builds run on CodeBuild on-demand.If you choose to set your overflow behavior to on-demand while creating a VPC-connected fleet, make sure that you add the required VPC permissions to your project service role. For more information, see Example policy statement to allow CodeBuild access to Amazon Web Services services required to create a VPC network interface.
IO_VPCCONFIG
TYPE REF TO /AWS1/CL_BLDVPCCONFIG
/AWS1/CL_BLDVPCCONFIG
¶
vpcConfig
IO_PROXYCONFIGURATION
TYPE REF TO /AWS1/CL_BLDPROXYCONFIGURATION
/AWS1/CL_BLDPROXYCONFIGURATION
¶
The proxy configuration of the compute fleet.
IV_IMAGEID
TYPE /AWS1/BLDNONEMPTYSTRING
/AWS1/BLDNONEMPTYSTRING
¶
The Amazon Machine Image (AMI) of the compute fleet.
IV_FLEETSERVICEROLE
TYPE /AWS1/BLDNONEMPTYSTRING
/AWS1/BLDNONEMPTYSTRING
¶
The service role associated with the compute fleet. For more information, see Allow a user to add a permission policy for a fleet service role in the CodeBuild User Guide.
IT_TAGS
TYPE /AWS1/CL_BLDTAG=>TT_TAGLIST
TT_TAGLIST
¶
A list of tag key and value pairs associated with this compute fleet.
These tags are available for use by Amazon Web Services services that support CodeBuild build project tags.