Executing Multiple Pipeline Instances Simultaneously




  • Avatar
    Ian Bridson

     Hi Kirk

    One constraint i can think of that could stop multiple executions is the number of available agents. Do you have more than one agent with suitable resource and environment settings that can pick up this pipeline? if not then Go will wait until the agent is free before triggering the pipeline properly.

  • Avatar
    Shilpa Goley

    Hi Kirk,

    Do you have only one stage in the pipeline?

    If so, then yes, you will not be able to execute pipeline instances parallely, because Go cannot be running the same stage in more than one pipeline instances parallely.


  • Avatar
    Vogen, Kirk (STP)

    Thanks for the comment -- very helpful. I have two stages so far in my experimental pipeline. It turns out it does let me start another pipeline instance as long as the currently executing one is on the second stage. Thanks.

    This makes me wonder why it doesn't allow a given stage to execute in parallel. Take the example where your first stage is a commit build that takes approximately three minutes to run. If you want this to run for each change set, it would seem that builds would soon back up.

    It looks like this post already discusses the issue of parallel stage execution.

  • Avatar
    Brian Warsing


    I was always confused about this feature. The documentation is scant and seems to describe a pipeline's ability to run "copies of itself" which is actually what I was hoping to do. As I now understand it, a single pipelines can be executed multiple times, but only if the first stage is currently executing...

    You cannot run multiple parallel instances of a single stage pipeline.

    Too bad...



Please sign in to leave a comment.