Hi community, Every developer in our organization gets a pipeline of his own to do the full build and test process. Very frequently we are making changes that have to be replicated across all pipelines, for example adding a new material, adding an additional step, minor changes in the command syntax of one of the steps in pipeline. Since each developer is supposed to maintain their own pipeline, they realize it only when the pipeline breaks because of this change and we are in a continuous maintenance loop.
Our need is to easily replicate these changes across all pipelines. Most configuration is same except the name of the pipeline is different. Whats the community recommendation for this. How else to manage this situation? Warm regards, Pankaj -- 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/f66ff769-da55-4383-9d55-7d5c201153fdn%40googlegroups.com.
