Node Pools provide a convenient way to logically group build nodes in a JFrog Pipelines environment. This enables you to run steps simultaneously on different nodes.
Administrators may create any number of node pools. For SaaS deployments, a node pool named
default-dynamic-nodepool is available by default. For self-hosted deployments, at least one node pool must be added and designated as the default node pool, and assigned at least one build node for pipelines to execute in the selected Project.
A node pool must be designated to contain build nodes of one of these types:
Dynamic Nodes - Build nodes that are spun up and down on-demand by Pipelines from a cloud or Kubernetes service. This can help scale operations, and help manage costs by not incurring cloud service charges to run idle nodes.
Static Nodes – Build nodes (virtual machines) that are persistently available through a fixed IP address.
For information about the minimum requirements for a static node that can be assigned to JFrog Pipelines and to learn how static nodes can be added, see Managing Pipelines Static Nodes.