I found a bug which is causing me to never be able cancel a build and thus delete a pipeline.
Bug:
build cannot be stopped due to a triggered pipeline always showing as running (even though it isn't anymore). When manually cancelling the build, the pipeline always remains on “Cancelling”.
How to replicate:
I triggered pipeline B from pipeline A. Pipeline B has a block step, and the block_state of this step was set to “Running”. Pipeline A has to wait for B to go from Running -> Passed. Even when manually unlocking pipeline B, pipeline A will always see pipeline B as still running, so the status never changes. This in turn makes it impossible for a job to finish or to cancel it.
This bug was uncovered when trying to get the blocked state of a triggered pipeline, which you're not able to do on Buildkite yet (at least so it seems).
Hi!
I found a bug which is causing me to never be able cancel a build and thus delete a pipeline.
Bug: build cannot be stopped due to a triggered pipeline always showing as running (even though it isn't anymore). When manually cancelling the build, the pipeline always remains on “Cancelling”.
How to replicate: I triggered pipeline B from pipeline A. Pipeline B has a block step, and the block_state of this step was set to “Running”. Pipeline A has to wait for B to go from Running -> Passed. Even when manually unlocking pipeline B, pipeline A will always see pipeline B as still running, so the status never changes. This in turn makes it impossible for a job to finish or to cancel it.
This bug was uncovered when trying to get the blocked state of a triggered pipeline, which you're not able to do on Buildkite yet (at least so it seems).