BF 7.1.2.2 - behavior change is not acceptable
What was the justification for changing the 'continue on fail' functionality to continue executing additional commands in the same step?
These seems very problematic, especially within our build process... I have a set of steps that are each dynamically generated and run threaded, up to 6 at a time; how do I use the suggested method of adding a separate step for the second command when it is specifically related to the step it was part of and may or may not run next?
These seems very problematic, especially within our build process... I have a set of steps that are each dynamically generated and run threaded, up to 6 at a time; how do I use the suggested method of adding a separate step for the second command when it is specifically related to the step it was part of and may or may not run next?
3 answers
What was the justification for changing the 'continue on fail' functionality to continue executing additional commands in the same step?
These seems very problematic, especially within our build process... I have a set of steps that are each dynamically generated and run threaded, up to 6 at a time; how do I use the suggested method of adding a separate step for the second command when it is specifically related to the step it was part of and may or may not run next?
Hi Steve,
It sounds like you ran into this defect.
https://jazz.net/jazz08/web/projects/Rational%20Build%20Forge#action=com.ibm.team.workitem.viewWorkItem&id=21055
The defect comments have a great description. Essentially, it appears there will be a sys config to choose whether to continue the step part on fail or not.
Brent Ulbricht
Developer/Lead - RTC Build