Config repository plugin issue (define multiple pipelines named)

[Sifu Tian]

Hi all,

I'm scratching my head on the errors that keep getting generated in the config repository plugin.

The error below is repeated for various pipelines.  There arent any duplicate pipelines.

All yaml files were downloaded from GoCD and merged into our repository.  

How can there be a configuration issue if the yaml files are from GoCD itself?

File pattern is **/*.gocd.yaml

INVALID MERGED CONFIGURATION Number of errors: 208+ 1. You have defined multiple pipelines named 'Common-build'. Pipeline names must be unique. Source(s):

Any help would be greatly appreciated

[Chad Wilson]

If you exported YAML from manually crafted pipelines in GoCD and then put that YAML in a config repository with the same names, you'd need to delete the ones manually defined in GoCD first.

From GoCD's perspective pipelines, materials etc whose config is in an external source-controlled config repo (pipelines as code) are differently managed to those manually defined in GoCD itself (and ending up in cruise-config.xml), so they are likely duplicate from GoCD's perspective (one manually constructed, one defined by a repository). GoCD needs to know the source to apply rules (e.g config repo pipelines are not editable via the UI) and the pipeline name is its unique ID so these have to be "globally unique" regardless of the source they are defined.

-Chad

--
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/d7f6a2ac-a333-4c2d-b2c7-f00eb89530a6n%40googlegroups.com.

[Sifu Tian]

Hi Chad,

Makes total sense and yes thats how they were created; manually.

Thanks for the info!

Kris