Allow me to control concurrency of tasks

Comments

3 comments

  • Avatar
    Deepthi Chandramouli

    Hi Mark,


    This is one of the features in our upcoming 2.0 release.


    Cruise now lets you lock a pipeline. This means that at any point of time, only once instance of a pipeline can be in progress. This feature combined with pipeline dependencies should solve the use case you have mentioned.


    It is ideal to be able to lock a set of stages(example: stage1, stage2 and stage3) and not the entire pipeline, so that when stage2 is building, stage1 cannot be entered, nor can stage3 of any other instance be run. We have this identified to be played in one of our 2.x releases; 2.0 will not have this implemented.


    So it is possible to model your use case such that the deployment happens as part of one stage and the twist tests are part of a separate subsequent stage. The pipeline containing these stages can be locked. This ensure that at any point of time only 1 stage can be active across all pipeline instances.


    Thanks


    Deepthi

    0
    Comment actions Permalink
  • Avatar
    Mark Crossfield

    Hi Deepthi. Thanks for your feedback.


    I understand from that that to achieve this in release 2.0 I would have to have these two stages separated into their own pipeline, so that that pipeline can be locked? And then later on in a 2.x release I will be able to do it with two adjacent stages??


    Many thanks, Mark

    0
    Comment actions Permalink
  • Avatar
    Deepthi Chandramouli

    Hey Mark,


    Yes, that is correct. For now you will have to have a pipeline with the two stages and lock the pipeline.


    Hope this helps.


    Deepthi

    0
    Comment actions Permalink

Please sign in to leave a comment.