Problem with Execution variables in first environment

[Dave Clarke]

We are using Buildmaster 4.0.8 (build 31) and have created execution variables for each of our environments and set them to require a value with no default.

If we create a new build and leave the checkbox "Promote New Build to First Environment" ticked we never get asked to enter the variables. Propmtion to subsequent environments does ask for the variable value.

If we create a new buuild and untick the "Promote New Build to First Environment" checkbox, then click "Promote to DEV" we can enter the vaiable values.

Thanks
Dave

[Tod]

This is 95% implemented, but will not be available until v4.1 because it requires an API breaking change in the Builds_CreateBuild procedure to pass the execution variables in.

In the meantime, it looks like you've found the workaround :) You can also use Promotion variables (which already are available on that page) for the first environment instead of Execution variables, since it is very rare to re-execute a build in the first environment since you can just create a new build instead.

[Dave Clarke]

Thanks, in our case the variables do not actually get used in the first environment, they are entered for consistency. Good to know it will be fixed in the future.