...
The Attributes are optional data that you can use to give different values to executions based on which branch you built from.
...
Subversion Source Configurations
...
First approach works well if you have a single Subversion repository. If you have multiple Subversion repositories in your environment, then you can utilize second approach to configure project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in Subversion configurations will be empty initially, and when user selects SVN Instance, configuration values will be defaulted appropriately.
...
All Git project sources will get same values (including Git Instance), or
you You can configure defaults by Git Instance. First approach works well if you have a single Git repository.
If you have multiple Git repositories in your environment, then you can utilize the second approach to configure the project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in Git configurations will be empty initially, and when user selects Git Instance, configuration values will be defaulted appropriately.
...
All CVS project sources will get same values (including CVS Instance), or
you You can configure defaults by CVS Instance. First approach works well if you have a single CVS repository.
If you have multiple CVS repositories in your environment, then you can utilize the second approach to configure the project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in CVS configurations will be empty initially, and when user selects CVS Instance, configuration values will be defaulted appropriately.
...
All TFVC project sources will get same values (including TFVC Instance), or
you You can configure defaults by TFVC Instance. First approach works well if you have a single TFVC repository.
If you have multiple TFVC repositories in your environment, then you can utilize the second approach to configure the project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in TFVC configurations will be empty initially, and when user selects TFVC Instance, configuration values will be defaulted appropriately.
...
All PVCS project sources will get same values (including PVCS Instance), or
you You can configure defaults by PVCS Instance. First approach works well if you have a single PVCS repository.
If you have multiple PVCS repositories in your environment, then you can utilize the second approach to configure the project based on some criteria. You can accomplish this by placing an "if" statement within Groovy script for the defaults. With this approach all attributes in PVCS configurations will be empty initially, and when user selects PVCS Instance, configuration values will be defaulted appropriately.
...