Every step in your pipeline executes on a build node that has been provisioned with a runtime environment. Through Pipelines DSL, you can control which runtimes your steps execute in.
By breaking up your pipelines into steps, Pipelines can distribute the work to wherever it can get done on the network. An administrator user must configure Pipelines with sets of build nodes (virtual machines) that are available for executing steps.
Pipelines sends each step to a build node to execute in a runtime, which is either the build node's virtual machine or a container provisioned with a Docker image on the build node. The runtime must have the necessary OS, software tools, packages, and configurations that the step needs to execute.
Running steps in series: When steps in a pipeline must execute on the same build node, they can be assigned to the same affinity group. For more information, see Running multiple steps on the same build node.
Running steps in parallel: Steps can be run in parallel to speed up pipeline execution. For more information, see Breaking Your Pipelines into Steps.
The following topics provide more information about JFrog Pipelines in Runtime :
Additional Information on Runtimes
The following additional information is available on Runtimes.