Mark Ready for Release - Go Pipes

[Nitesh Kumar]

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

[Sriram Narayanan]

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

--
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 go-cd+un...@googlegroups.com.
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.

[Nitesh Kumar]

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

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CANiY96Yf1y8PPenghtjXh5Vqt8dBtXW4pqVD6xC%3DML1%3DjJie6A%40mail.gmail.com.

[Nitesh Kumar]

Hi,

Request you all to please help on this

[kritik...@thoughtworks.com]

Hey Nitesh,

> I need know that do we have  any GOCD API is available to trigger the stage ?

There is an API to trigger stage: https://api.gocd.org/current/#run-stage - I hope this is wht u were looking for.

Regards

Kritika

[Ashwanth Kumar]

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,

--

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 go-cd+un...@googlegroups.com.
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.

--

Ashwanth Kumar / ashwanthkumar.in

[Nitesh Kumar]

Hi  Kritika,

Thanks , but i think this is only available in latest version , i am using 17.4.0 , do we have available on this version ?

--
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 go-cd+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/22c74a9d-afc5-489f-9b8f-beaacc643392n%40googlegroups.com.

--

Thanks&Regards

Nitesh kumar

[Nitesh Kumar]

HI  Ashwanth ,

Thanks ,

this what we have in current system, but we are changing our current where we have to trigger our 100 Pipes ( dev environment ) and after Dev validation we need mark approval stage for these 100 + pipes in one go. that is why  need any API which can help us by filling our requirements.

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/CAD9m7CweiF_knLWYStxdZ82_4Am4-x6txfHuskXVGV7Rt1Og9A%40mail.gmail.com.

--

Thanks&Regards

Nitesh kumar

[kritik...@thoughtworks.com]

Hi Nitesh,

> Thanks , but i think this is only available in latest version , i am using 17.4.0 , do we have available on this version ?

No this API was introduced in `v18.11.0` .

Regards

Kritika

[Nitesh Kumar]

Hi All,

Do we have any GO API which help us to get the latest version of the Pipeline ?

Regards, Nitesh 

--
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 go-cd+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/5d8d7238-d47b-4be5-b2f1-de28af849dd3n%40googlegroups.com.

--

Thanks&Regards

Nitesh kumar

[Jason Smyth]

Hi Nitesh,

You can get documentation for the APIs for your version of GoCD (17.4.0) here: https://api.gocd.org/17.4.0/#introduction.

With that said, unless you have some really compelling reasons for staying on 17.4, you should probably consider upgrading to a more current version.

Regards,

Jason