If we are going to go down the road of generating XML configuration from a template + parameters we should consider a using a proper templating language, making the name of the template configurable so the user can supply their own, and supplying data as a map to allow the user to pass in arbitrary data necessary for their template. However, I believe it might be wise to leave the template rendering to a separate library (since there are many ways to solve this problem with various pros and cons), and keep jenkins-client independent of how the config.xml is generated.