| Key: |
QB-2362
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Robin Shen
|
| Reporter: |
AlSt
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 10/Mar/15 10:29 AM
Updated: 19/Mar/15 11:19 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
5.1.40
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
|
In my case the referenced QB configuration (why a script) really does not exist, and this is also the reason why I tried to "guard" the "trigger other build" step with the execute condition to skip it. And while it appears to be skipped, the build fails nonetheless.
Please note that the failure log is stemming from the script and looks like:
mvel:configuration.parent.parent.getChild("linux-x86-32").getChild(configuration.name).pathName
|
|
Description
|
In my case the referenced QB configuration (why a script) really does not exist, and this is also the reason why I tried to "guard" the "trigger other build" step with the execute condition to skip it. And while it appears to be skipped, the build fails nonetheless.
Please note that the failure log is stemming from the script and looks like:
mvel:configuration.parent.parent.getChild("linux-x86-32").getChild(configuration.name).pathName |
Show » |
|
Build fails, if the configuration of a "trigger other build" step does not exist, even if this step is skipped based on the execute condition
