We have several projects in our organization where we have configured Jenkins Templates to be used. Certain projects do require certain features rolled out at a later point of time.
For example, Project X requires templating configuration:v1.0.0 and Project Y requires templating configuration:v1.0.1. This feature is rather important and a much cleaner approach than using folders for different versions because it does not lead to the duplication of code (as in folders) and easier to maintain.
That is why, configuring templates with tags would be a really good idea in every project. One can make this as an optional field.
Feature Description
We have several projects in our organization where we have configured Jenkins Templates to be used. Certain projects do require certain features rolled out at a later point of time. For example, Project X requires templating configuration:v1.0.0 and Project Y requires templating configuration:v1.0.1. This feature is rather important and a much cleaner approach than using folders for different versions because it does not lead to the duplication of code (as in folders) and easier to maintain. That is why, configuring templates with tags would be a really good idea in every project. One can make this as an optional field.