Stage Groups Support
next fiscal quarter
A
Aesthetic Gecko
i would like to run the stage group (build and deploy in QA) in parallel of a another stage that is "change management" like the photo attached (I can do it in Azure DevOps). as change mgmt is only needed in prod, but can be completed since the build process.
Log In
Rohan Gupta
next fiscal quarter
F
Firm Anglerfish
+1 this will be helpful to us as well
Rohan Gupta
Merged in a post:
Stage Group Possibility
Z
Zinc Peacock
Hello,
I would like to suggest the possibility to create 'Stage group', as there is the possibility to create 'Step group'.
It can be easier to create a condition execution for all a stage group (based on a runtime variable value for example).
Rohan Gupta
Merged in a post:
Group multiple stages to run them in parallel when calling another pipelines.
E
Environmental Cuckoo
We have a requirement where team wants to have 2 set of parallel stages into a group and want to execute them in the sequence specified, rather than waiting for the 1st parallel stage to complete.
Note: Each of the stages is calling another pipeline.
Currently team has to wait until all generate stages is finished and then the modify stages will start.
They want the modify stages to start as soon the corresponding generate stage is finished
There are 3 generate stages and 2 modify stages in this example.
Current behavior:
Our users have to wait for all the generates stage to finish to start with the modify stage.
Expected behaviour:
We want a way that modify stage starts as soon as its corresponding generate stage is finished.
eg: As soon as Generate IDS Pod stage is completed, Modify RDS IDS Stage should start without waiting for other generate stages to finish.
Support ticket: https://support.harness.io/hc/en-us/requests/59095
Rohan Gupta
Merged in a post:
Need a way to club multiple parallel stages
E
Environmental Cuckoo
We have a requirement where team wants to 2 set parallel stages into a group and want to execute them in the sequence specified, rather than waiting for the 1st parallel stage to complete.
Note: Each of the stages is calling another pipeline.
There are 3 generate stages and 2 modify stages in this example.
Current behavior:
Our users have to wait for all the generates stage to finish to start with the modify stage.
Expected behaviour:
We want a way that modify stage starts as soon as its corresponding generate stage is finished.
eg: As soon as Generate IDS Pod stage is completed, Modify RDS IDS Stage should start without waiting for other generate stages to finish.
Rohan Gupta
long-term
I
Iron grey Chicken
Rohan Gupta could you please define what does LONG-TERM signify? is it 6 Months, 1 year, 2 years? by when should we expect availability of this feature? already more than 6 months have passed since this was requested.
Prasad Satam
pending feedback
A
Aesthetic Gecko
Prasad Satam: It doesn't make sense to give feedback on an unimplemented feature.
Prasad Satam
under review
Thank you Claudio for the detailed explanation, I will review this idea again and get back.
Prasad Satam
complete
Hello,
Harness addresses this scenario using Barriers. Barriers allow you to synchronize different stages and step groups in your Pipeline, and control the flow of your deployment systematically. For more information about barriers, please go through this doc - https://developer.harness.io/docs/continuous-delivery/x-platform-cd-features/cd-steps/flow-control/synchronize-deployments-using-barriers/
A
Aesthetic Gecko
Prasad Satam:
Hi,
I don't know if you understood the request correctly, the stages do not occur in parallel but rather asynchronously, however at a certain point one stage is dependent on another having already been executed.
The documentation explains that the stages are in parallel and that the steps will synchronize within one or more stages.
Is my understanding wrong?
diego.pereira@harness.io
Prasad Satam: you should put it back in review and remove as complete.
diego.pereira@harness.io
Prasad Satam: In the image Claudio shared in the feature request, the second stage should be structured to interact with the entire pipeline from the very beginning up until the fourth stage. This means the second stage runs in parallel with the first three stages. However, it's only at the fourth stage where this parallel stage fully integrates or merges into the main process. This setup allows for continuous interaction of the second stage with the initial stages, ensuring a more integrated and cohesive workflow until it converges in the fourth stage.
For the customer to effectively implement the desired pipeline structure, they need the capability to group the first three stages. Once this grouping is established, it would then be possible to run the second stage in parallel with this collective group. Currently, we have the functionality to execute steps and step groups in parallel, but this feature needs to be extended to stages.
This will provide the flexibility and control needed for complex pipeline configurations like the one described.
Prasad Satam
under review
Load More
→