| << Back to previous view |
|
[QB-1617] Step with Empty Repeat Parameters is not shown in Build Step status
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 5.0.18 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Noam Manos | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
It took me a while to understand why I have a step with Repeat Parameters (script), that does not shown in the step status after build completed.
If Step has Repeat Parameters script that returns a list of params, the step status is shown at the end, but I would have expected to see a step status such as "skipped" or "not executed" if the Step has Repeat Parameters script that returned an empty list, such as: ${groovy: buildModes = ""; if (params.get("TestParameters").matches(".*ARCSound@Debug.*")) { buildModes += "debug,"; \} if (params.get("TestParameters").matches(".*ARCSound@Release.*")) { buildModes += "release,"; \} logger.warn("Build Modes = " + buildModes); return buildModes; } Only after I added the logger.warn I saw that buildModes was empty, but it is not understood from the step status - where the step is simply missing. |
| Comments |
| Comment by Robin Shen [ 06/May/13 10:59 PM ] |
| This is designed to be so as if you loop through an empty list in any language, nothing will be executed and logged. Also step condition is evaluated in each run of the parameter so there is no chance for QB to log it as "skipped". |