After some investigation, we found that in order to display the details of sub condition matches, we have to list the reason for every node in system, something like below:
node1: sub condition1 matches, sub condition2 does not match
node2: sub condition1 does not match
...
nodeN: ...
Since this information should be stored in step level, and every running build may have several steps containing this info, it will consume a lot of spaces if there are hundreds of nodes, which may hurt the system performance seriously. So we put this off unless there are some other approaches available.
Robin Shen[21/Dec/13 02:22 PM]
After some investigation, we found that in order to display the details of sub condition matches, we have to list the reason for every node in system, something like below:
node1: sub condition1 matches, sub condition2 does not match
node2: sub condition1 does not match
...
nodeN: ...
Since this information should be stored in step level, and every running build may have several steps containing this info, it will consume a lot of spaces if there are hundreds of nodes, which may hurt the system performance seriously. So we put this off unless there are some other approaches available.
Improvement
Open
Minor
Enhance error report to report details of sub conditions when failed to find matched node for a step
node1: sub condition1 matches, sub condition2 does not match
node2: sub condition1 does not match
...
nodeN: ...
Since this information should be stored in step level, and every running build may have several steps containing this info, it will consume a lot of spaces if there are hundreds of nodes, which may hurt the system performance seriously. So we put this off unless there are some other approaches available.