Hi everyone, We have a GoCD instance with about 1200 pipelines, most of which are defined directly in the GoCD configuration XML file. Of the pipelines that are defined in the XML config, most are based on templates.
We are trying to migrate most, if not all, pipelines into (a) configuration repo(s), with the thought being to abandon templates altogether. Our management of templates has been poor historically, leading to template sprawl. We have 439 templates, of which 122 are unused. Exporting pipelines to JSON or YAML is perfectly straight-forward. However, for pipelines that are based on templates, the export retains the template reference. Is there a way to export the de-normalized pipeline definition so that we do not have to hand-craft the JSON/YAML structure for each template? I came across this GitHub issue <https://github.com/gocd/gocd/issues/5725>. I am inclined to agree with the author that the correct default behaviour for export is to maintain the template reference; that is the true representation of the pipeline's configuration. However, since we are looking to move away from using templates, it would be nice if there were an easy way for us to export the merge of the pipeline and its associated template. I also came across this mail list conversation <https://groups.google.com/g/go-cd/c/A-S27utXZ0M/m/65_bwmrqBwAJ> but it, along with the links it contains, is mostly about support for templates defined in the config repos. Does anyone have any ideas on how we can easily accomplish our goal? Any thoughts or guidance welcome. Regards, Jason -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/e3cd8df8-7463-4069-b495-9a48d6617099n%40googlegroups.com.
