Hi Sriram, Thanks for the response, I am already using the same approach A to get my pipes deployed in higher environments.
My current situation is , I have around 100 pipes and one common stage in all pipes I.e ready to release. Which enables the specific version for higher environments. But I have to do that manually now. I need know that do we have any GOCD API is available to trigger the stage ? Regards, Nitesh On Sun, 17 Jan 2021, 15:52 Sriram Narayanan, <[email protected]> wrote: > A pipeline should be associated with one environment (I'm not talking > about GoCD's environments here). > > You may want to consider one of the following approaches: > a. An environment's pipeline that is manually triggered, and which uses an > earlier pipeline as it's material. (e.g. a Prod deploy pipeline that uses > the staging pipeline as a material.). Only the agreed-upon pipeline number > from staging would be used in Prod. > > b. If you have multiple pipelines that have to go live together, then > create one downstream pipeline that all of these join to. Then use that > pipeline number for all further environments. e.g. Web -> Bundle, Backend1 > -> Bundle, Backend2 -> Bundle . In the Bundle pipeline, set the trigger to > be manual, use Trigger with Options to select which versions of the Web, > App1 and App2 pipelines you want to use, and then refer to that Bundle > version for all downstream environments. > > c. For teams that have a test suite that can test across Web, App1 and > App2 (the scenario above), I'd change "Bundle" above to "Acceptance Test". > Meaning, "So and so combo of web + app1 + app2 have passed this acceptance > test suite and can be used in all further environmental". > > d. If you want to release them all independently, then it may be a simple > matter (in terms of pipeline) to just have Web -> ApproveWebForProd -> > WedProdDeploy, App1 -> ApproveApp1ForProd -> AppProdDeploy, etc. This > presumes that the various tiers have their own contract tests to ensure > that if the App1 changes, then the test suite would flag any > incompatibilities/breaking changes with Web. > > -- Ram > > On Sun, Jan 17, 2021 at 5:41 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> >> . >> > -- > 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/CANiY96Yf1y8PPenghtjXh5Vqt8dBtXW4pqVD6xC%3DML1%3DjJie6A%40mail.gmail.com > <https://groups.google.com/d/msgid/go-cd/CANiY96Yf1y8PPenghtjXh5Vqt8dBtXW4pqVD6xC%3DML1%3DjJie6A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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_Unbj8sgHn6yhx62VWgk4%3DFxRkRHUV6cmxn-JEsckmkamA%40mail.gmail.com.
