To create a new node pool of static build nodes, go to Administration | Pipelines | Node Pools, click Add Node Pool, and then select Static.
Fields that are not required may be left blank. For example, you may not wish to set the fields to limit node count, disk usage, or timeout. When finished, click Save Node Pool.
An alphanumeric friendly name for the node pool.
Set as Default Node Pool
When checked, sets the node pool as the default node pool for all pipelines. All steps that do not explicitly define which node pool to use will run on nodes of the default node pool.
Currently limited to x86_64
Select from the list of operating systems supported for the selected architecture. For a list of supported OS and architecture combinations, refer to Runtime Images.
The default runtime image that will be used to run pipeline steps. Choose a specific runtime to make sure the build nodes have the versions you need for languages/services/CLIs/etc. To learn more, see Managing Runtimes.
Limits the maximum number of nodes that can be added to the node pool.
Max Disk Usage %
Limits the maximum disk usage. A build node that exceeds this maximum will be marked as failed.
The maximum time (in seconds) after which you want your pipeline steps to timeout. This timeout is used when your step does not have any timeout specified. Default value for timeout is 3600 seconds.
For more information, see Setting Step Timeouts.
Insecure Docker Registries
A comma-separated list of allowed insecure docker registries.
Assign Pipelines to this Node Pool
Any Pipeline Source
When selected, pipelines loaded from any pipeline source can use this node pool.
Unselect this option to restrict node pool use to a set of pipeline sources.
Once you have created a static node pool, you can add static nodes.