One way is to have a marker stage at the end of the pipeline (say Pipeline A) that is set to manual.
Now assuming a Pipeline B (high environment) is pulling the artifacts (or traversing through) from Pipeline A, we set it to be dependent on this manual stage. So unless the manual stage is approved on Pipeline A (which I'm hoping you would do as part of the release), Pipeline B will continue to pick the last approved version. Thanks, On Sun, Jan 17, 2021 at 3:11 PM Nitesh Kumar <[email protected]> wrote: > Hi , > > Do we have any option by which we can mark ready for release to multiple > GO Pipes in one go. > > Ready for Release - if we run this stage our Pipe get ready for higher > environment > > OR > > Do we have any option to trigger the stage of pipeline ? > Request you to please help on this > > > > -- > Thanks&Regards > > Nitesh kumar > > -- > You received this message because you are subscribed to the Google Groups > "go-cd" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/go-cd/CAKns_UkZG7i%3DizLxf%2B_Nn%2BLdF8merch0m7zmM0vtHsyvQ-kCxg%40mail.gmail.com > <https://groups.google.com/d/msgid/go-cd/CAKns_UkZG7i%3DizLxf%2B_Nn%2BLdF8merch0m7zmM0vtHsyvQ-kCxg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- Ashwanth Kumar / ashwanthkumar.in -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAD9m7CweiF_knLWYStxdZ82_4Am4-x6txfHuskXVGV7Rt1Og9A%40mail.gmail.com.
