Open configuration root.live-samples.usecase5, and check modules definition of its CVS repository setting, you'll find that label value of source path sample1 has the value of ${var["label"]}. And in the basic settings tab of this configuration, a variable label was defined with an empty value like this:
label=
It means that this configuration will still build against latest code unless you specify a non-empty value for the variable label.
Now forcibly trigger this configuration, in the appeared Editing manual trigger settings page, provides a different value for label variable like this:
label=myproduct-1_0_0
In this way, configuration root.live-samples.usecase5 is triggered to build against label myproduct-1_0_0.
![]() | Tip |
---|---|
By using variables, you can make almost any part of repositories, builders, or steps definition be overridable when manually triggers the build. Also it is possible to override these variables in child configurations, which gives you the flexibility to modify part of objects defined in ancestor configurations. |