I've got a simple pipeline (mirrors file contents to an FTPS site) which is tied to a Bitbucket Deployment. Pipelines often get stuck on "Queued" without even starting, even though the runner is ready and online.
Here's the tail of the Docker log for the container, after finishing a previous successful build:
[2021-05-05 16:14:56,273] Completing step with result Result{status=PASSED, error=None}.
[2021-05-05 16:14:57,534] Setting runner state to not executing step.
[2021-05-05 16:14:57,535] Waiting for next step.
[2021-05-05 16:15:11,876] Setting runner state to executing step.
[2021-05-05 16:15:19,845] Updating runner state to "ONLINE".
[2021-05-05 16:15:49,844] Updating runner state to "ONLINE".
[2021-05-05 16:16:19,844] Updating runner state to "ONLINE".
[2021-05-05 16:16:49,844] Updating runner state to "ONLINE".
[2021-05-05 16:17:19,844] Updating runner state to "ONLINE".
[2021-05-05 16:17:49,845] Updating runner state to "ONLINE".
[2021-05-05 16:18:19,846] Updating runner state to "ONLINE".
[2021-05-05 16:18:49,845] Updating runner state to "ONLINE".
[2021-05-05 16:19:19,846] Updating runner state to "ONLINE".
[2021-05-05 16:19:49,845] Updating runner state to "ONLINE".
[2021-05-05 16:20:19,846] Updating runner state to "ONLINE".
[2021-05-05 16:20:49,844] Updating runner state to "ONLINE".
[2021-05-05 16:21:19,846] Updating runner state to "ONLINE".
[2021-05-05 16:21:49,844] Updating runner state to "ONLINE".
[2021-05-05 16:22:19,845] Updating runner state to "ONLINE".
[2021-05-05 16:22:49,844] Updating runner state to "ONLINE".
[2021-05-05 16:23:19,845] Updating runner state to "ONLINE".
If I forcefully stop and start the runner, the pipeline picks it up and runs it right away.
Has anyone else experienced this? Could it be related to the fact I've got a dependency on a Deployment?
Chad Gilbert
10 comments