Is it possible to make a dynamic child pipeline optional based on the outcome generate config job in the parent pipeline?
So if the generate config job generates an empty pipeline and no artifact that the child pipeline is skipped? I have tried to do this with rules, but my pipeline generate script is more complex than the rules are able to handle.
My current work-around is to generate a dummy child pipeline.
So what I would like to do is if the generate config jog produces no pipeline (no artifact) then the child pipeline should be skipped.