Skip to content

Better Variable Matching
Compare
Choose a tag to compare
@BobJWalker BobJWalker released this 03 Nov 16:06
v1.6.0
26ac8c9

The variable matching with previous releases was too simplistic and resulted in variables not being cloned over. The variable matching logic has been re-written to now match a source variable with a destination variable by comparing.

  • Name
  • Sensitive vs non-sensitive
  • Environment Scoping
  • Machine Scoping
  • Role Scoping

For projects, additional scoping matching is added

  • Process Scoping
  • Step Scoping
  • Channel Scoping

If you modify the scoping on the source, or change from sensitive to non-sensitive (or vice versa) the cloner will see that as a new value and attempt to copy it over.

Because of this updated logic the parameter AddAdditionalVariableValuesOnExistingVariableSets has been removed.

Assets 2
Loading