Hello Kritika, thank you for the link to the discussion (which is closed). I see that managing of the templates can be a little more complicated as I thought. I only had my usecase in mind which implied that referencing pipelines will always use the current implementation of the template and not some fixed version of the template from the past. But the current implementation of templates in GoCD doesn't support this either. If you think the mentioned versioning concept of pipeline templates a little bit further you will come to the conclusion, that you need this for pipelines too. You have some upstream / downstream pipeline dependencies which might only work with some fixed pipeline version, e.g. the artifacts may change in an upstream pipeline and then the downstream pipeline will stop working.
For me it would be totally valid to resemble the current behaviour of GoCD in a "Pipeline Templates as Code" scenario. PS: Versioning of templates could be easy too ... If you introduce a breaking change then create a new template and put a "V2" at the end of the name ;) Regards Helge -- 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/ae3745ac-b528-41a3-8128-bcda29297949o%40googlegroups.com.
