Perhaps pipeline templates <https://docs.gocd.org/current/configuration/pipeline_templates.html> and parameters <https://docs.gocd.org/current/configuration/admin_use_parameters_in_configuration.html> could help you? (Both are supported by YAML cofig repo if you still wanted to go that route.)
On Tue, Feb 20, 2018 at 2:17 PM, Andrew Jones <[email protected]> wrote: > Our build pipeline includes builds of our main project in multiple > configuration/platform combinations (eg: Release/x64, Debug/x64, > Release/RISC, Debug/RISC). We currently handle this by duplicating the > contents of the job (each copy setting environment variables differently), > but this creates a maintenance issue when we need to make changes to the > job. I believe I could use the YAML config repo to do this but support for > anchors & aliases in gocd-yaml-config-plugin is undocumented. How have > others handled similar requirements in their build pipelines? > > Because of the size of our solution building all configuration/platform > combinations within a single job (via a batch file or similar scripting) > would not work. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
