How to ensure all the steps of a pipeline is executed on the same runner

[DARSHAN GAD]

On my self hosted runner, I am running a pipeline that consists of several steps. I noticed that the steps are randomly executed on different runners running on different servers.

But I want to run the entire pipeline on the same self hosted runners, otherwise it will fail due to missing dependencies from the previous steps.

How can I ensure that once a pipeline starts, all the steps are executed on the same runner?

[Mark C]

Hi @DARSHAN GAD,

Welcome to the community.

Would it be possible for you to let me know what type of runners you're currently using?

Regards,
Mark C

[DARSHAN GAD]

@Mark C , Thank you. I am using a self.hosted linux.shell runner.

runs-on:
- self.hosted
- linux.shell

Regards,

Darshan

[Mark C]

Hi @DARSHAN GAD

Thanks for the confirmation.

If you're using multiple runners, could you try to use a single runner?

Regards,
Mark C

[Paul Hicks]

I'm keen to know the answer to the original question too. I would not be able to use a single runner: I want to be able to run multiple pipelines at once, and to have all steps with matching runs-on properties to run on the same runner. Being able to set `clone: enable: false` on steps would greatly speed things up.

To make things a bit more complicated, my pipelines have Linux self-hosted, Windows self-hosted, and normal in-cloud steps. I would like to be able to rely on the file system for steps running on self-hosted runners persisting for the duration of the pipeline.