Ability to choose selective stages and save it as a part of input set
long-term
D
Distinct Rook
Currently when using the selective stage execution https://developer.harness.io/docs/platform/triggers/selective-stage-execution-using-triggers/#execute-a-specific-pipeline-stage-using-triggers , the stages can be selected when executing the pipeline. Currently there isn't an option to set a delegate selector as a part of input set. This request is to add the selective stages within an input set so that using an specific input set with selective stages is sufficient.
Log In
Rohan Gupta
Merged in a post:
Selective Stage Runs in Triggers
A
Agreeable Duck
In our triggers, on the last configuration page, we can select which stages we want to run. If we manually select all the stages, the end YAML defaults us to All Stages however, this isn't necessarily what we want. We use a template and will add stages to this template. We don't want the new stages we've added to be ran when the pipeline triggers. Instead, we want the list to be static and definitive instead of dynamically adding all the stages. Currently the only workaround is to manually edit the YAML and add the stages in manually but, this will cause issues with managing these triggers as we continue to add more stages to our templates. Can we make it so that in the UI, if the user manually checks every stage we are not defaulting it to All Stages and instead only adding a list of the selected stages?
Autopilot
Merged in a post:
Selective stage for pipeline chaining
L
Likely Turtle
Hi,
We are not able to select which stages to execute in the pipeline when it is added as a stage. Can this be raised as a feature request?
Thanks
Autopilot
Merged in a post:
Allow selective stage execution from Inputsets
P
Psychological Firefly
I have a pipeline that I plan to only execute manually, but would like to implement selective stage execution depending on which inputset is run, without relying on triggers
Rohan Gupta
Merged in a post:
Feature Request: To allow only selective stage to be triggered with triggers
G
Grateful Caribou
While a pipeline is triggered with trigger, it executes all the stages. We would like to add a option to choose what stages to execute like we can choose when we trigger the pipeline manually.
F
Frequent Jay
Yes please, +1. Example: We have a pipeline with two stages, "Build" and "Test". We want to save an inputset named "Hotfix" which is triggered on branches matching
hotfix/*
which selectively only runs buildYes, ik its technically possible today with custom variables and conditional execution. BUT in a pipeline with 10s of stages, its lots of bloat. And since harness already natively supports stage selection, let us persist that selection into inputsets.
The current UI is confusing anyways. If you "Run" a pipeline and select stages, then "save to new input set", it seems to imply that the selection will be persisted too, but it isn't.
Rohan Gupta
marked this post as
long-term
Rohan Gupta
Merged in a post:
Selective Stage Execution within a Child Pipeline of a Parent Pipeline
D
Distinct Rook
I'm running a child pipeline as a stage inside of a parent pipeline and I want to selectively execute certain stages from the child pipeline. Right now I plan on doing this by making all the stages' conditional executions an input value. But I saw the "selective stage execution" feature and it seems like it can only be used on triggers or manual pipeline runs. Is there anyway this information can be put into an inputset and be used to selectively execute stages?
Sudarshan Purohit
marked this post as
pending feedback
Sudarshan Purohit
Hi Distinct Rook, sorry, could you please elaborate on the connection between the delegate selector and the selective stage execution? I'm not sure I understand how adding Stage names to the Input Set will help with the delegate selector input.
D
Distinct Rook
Sudarshan Purohit My fault, I misspoke. I didn't mean delegate selector, I meant stage selector. Basically I was wondering if I could use the "selective stage execution" feature in an inputset. Becuase right now, this feature is only available for triggers and manual pipeline runs.