Writing the script in the Execute Condition works, but a pair of combo-boxes to select the step and the status would improve the integrity of the configuration. When a step is renamed each instance of that script has to be changed by hand. Hard-coded string literals are inherently error-prone. If the step path specified in the script does not exist, I don't see even a warning in the build log so steps may be executing when they shouldn't, or not executing when they should, because someone made a typo or forgot to change a reference after a step was renamed.
Expanding on the existing selections of "node running previous sibling" and "node running parent" on option that gives me a combo-box of all preceding steps would be useful. We have a number of configurations that run steps in a parallel composition on nodes of different OS and arch, and then come back to the master step's agent, then do another parallel composition and want to use the same agents as the previous parallel composition. This way we avoid having to send files back and forth between nodes unnecessarily. It can be somewhat error prone though as the implementation is dependent on the script to specify a step path
|
