Weird .bset selector behavior
![]()
Hi,
I use a .bset selector command in an inlined step and it behaves the way it is described in the documentation: it affects all subsequent steps in the inlined project and not the steps that follow the step that calls the inlined project. However, that behavior changes when a project fails and is restarted. For some reason, when a project fails in a step that follows the step that executed the inlined project in which the selector was updated and is then restarted, the new selector is used! It appears .bset selector updates the default selector for the entire project, but only for subsequent executions of the same project run. Is this a know bug? We're running version 7.1.3.5. Thanks, Jozef |
One answer
![]()
Hey Josef,
This isn't something that I am aware. Although, I do agree with you. At this point, I would recommend opening a PMR so that support can follow the processes in place to determine the root cause and fix the issue.
Thanks!
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.