kind: pipeline type: docker name: parallel steps: - .... --- kind: pipeline type: docker name: serial steps: - .... depends_on: - parallel node: runner: single
We have two runners: an unlabeled one with
DRONE_RUNNER_CAPACITY=10 which is meant to execute the “parallel” pipeline, and one labeled “runner: single” which has
DRONE_RUNNER_CAPACITY=1. The idea is the “parallel” pipeline can run up to 10 different builds in parallel, while “serial” is gated to one build at a time on a specific runner. In practice it seems “parallel” won’t start until “serial” gets the queue (runner with “runner: single” starts processing the build, but correctly blocks on completion of the associated “parallel” pipeline).
Is this expected behavior, or a subtle bug in pipeline dependency management?