In a configuration the step "smoke" is a QB repository checkout step (latest build: generate new if necessary) with an execute condition "... && !(vars.get("skipSmoke") != null && vars.get("skipSmoke").asBoolean())". That is, setting the variable "skipSmoke" to "true" should allow skipping the step "smoke" for the sake of saving time.

However, the (QB repository) dependency (build) is seemingly executed before the dependent build and ignoring the execution condition.

Using the execution condition sounds like the perfect way to do this (as the logic is right where it belongs to).

What do you suggest?

A workaround like handing over the variable to the dependency build and in there checking the variable (master step execute condition) always leads to a new dependency build (independent of repository changes) due to the usage of variables IIRC.

Even thought I don't like this workaround because the logic is confusingly distributed: Would handing over the variable to the dependency build and extending the build condition of the dependency build to first check the variable value always lead to new dependency builds (independent of repository changes) in case it is not skipped?