I would just do what Ashwanth suggested with Environments: put your pipelines (and agents!) in the same environment and then you can apply these (e.g., environment variables) globally to all pipelines in that environment.
On Friday, January 8, 2021 at 6:37:26 AM UTC-8 [email protected] wrote: > Thanks, > Yes, these pipeline already exists. > > but updating the config XML every time when we will have new change from > client will be risky. > > request you to please help another way around ? > > On Friday, January 8, 2021 at 7:05:47 PM UTC+5:30 [email protected] > wrote: > >> IMHO, Environment in GoCD helps in grouping pipelines to provide >> environment related settings (via environment variables) or agents (that >> have environment specific access / configurations). A variable used in the >> pipeline's material isn't specific to an environment and also Parameters >> are specific to a pipeline. So much so, that when a pipeline is saved all >> the parameters that are referred within (either on config / jobs / stages) >> should be available else the config validation would fail and the new >> pipeline changes wouldn't get saved. >> >> For your current situation, I do have a few suggestions: >> 1. If you're creating the pipelines right now, I would recommend using >> the YAML / JSON DSL which would make your life easier. You can find and >> replace the values quickly. >> 2. If these 100s of pipelines already exist, During an off-peak time / >> with maintenance mode enabled -- You can import the config.xml locally and >> find-replace the material path and import the new config back as a one time >> migration. >> >> Thanks, >> >> >> On Fri, Jan 8, 2021 at 6:45 PM [email protected] <[email protected]> >> wrote: >> >>> Thanks , >>> >>> but i can't see any option to set parameter global to the environment , >>> do we have any other option ? >>> >>> i have got 100 pipes, where having same TFS path but dynamic change >>> number, which needs to concatenated with TFS path , so we want to execute >>> 100 pipes in one for different -different change number on adhoc basis. >>> >>> On Friday, January 8, 2021 at 6:32:24 PM UTC+5:30 [email protected] >>> wrote: >>> >>>> You could use Parameters for that purpose. >>>> >>>> On Fri, 8 Jan, 2021, 18:13 [email protected], <[email protected]> >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> is there any way we can use a lobal variable and use that variable in >>>>> my GO pipe Material path - like TFS repo path >>>>> >>>>> This is really urgent , and quick help will be very much appreciated. >>>>> Thanks in advance >>>>> >>>>> 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 [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/go-cd/aee436d7-9c27-4005-9d35-070aed4e048an%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/go-cd/aee436d7-9c27-4005-9d35-070aed4e048an%40googlegroups.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/80994bd0-3d71-4a8d-9bd6-a929c01bada3n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/go-cd/80994bd0-3d71-4a8d-9bd6-a929c01bada3n%40googlegroups.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/bb2b4175-d07b-4722-9a27-a0347ac83d83n%40googlegroups.com.
