Why Do Steps Not Show As "Skipped"?
Build Forge 8.0.0.1
In BF 7.1.3 when steps are skipped - the display shows exactly that - and the icon is gray. With BF 8.0.0.1, if the step is skipped the icon turns green as if the step has been executed and there are no words saying "skipped". In order to see if the step is truly skipped, you have to drill down into the console for that step and you'll see
"EXEC Empty command text for Step "
How do I get BF 8.0.0.1 to act like BF 7.1.3 and show which steps were skipped - on the step summary page?
Thanks,
John Bobinyec
In BF 7.1.3 when steps are skipped - the display shows exactly that - and the icon is gray. With BF 8.0.0.1, if the step is skipped the icon turns green as if the step has been executed and there are no words saying "skipped". In order to see if the step is truly skipped, you have to drill down into the console for that step and you'll see
"EXEC Empty command text for Step "
How do I get BF 8.0.0.1 to act like BF 7.1.3 and show which steps were skipped - on the step summary page?
Thanks,
John Bobinyec
One answer
This is causing further trouble. See defect 31153. I'll explain here as well.
BF 7.1.3
We have a step which is controlled by a condition. If the condition is met, the step is executed. It has a good return code, so this kicks off a chained job (on pass). If the condition is not met, the step is skipped and is never executed. So this is a way to control whether or not a chained job is executed.
BF 8.0.0.1
We have the same step. If the condition is not met, the following is executed:
"EXEC Empty command text for Step "
This empty command has a good return code and so the chained job is executed. This is exactly opposite of what was desired. The condition no longer controls the execution of the chained job, which ALWAYS executes.
Thanks,
John Bobinyec
BF 7.1.3
We have a step which is controlled by a condition. If the condition is met, the step is executed. It has a good return code, so this kicks off a chained job (on pass). If the condition is not met, the step is skipped and is never executed. So this is a way to control whether or not a chained job is executed.
BF 8.0.0.1
We have the same step. If the condition is not met, the following is executed:
"EXEC Empty command text for Step "
This empty command has a good return code and so the chained job is executed. This is exactly opposite of what was desired. The condition no longer controls the execution of the chained job, which ALWAYS executes.
Thanks,
John Bobinyec