| << Back to previous view |
|
[QB-185] properties not forwarded to triggered configration, Propogate variables to dependent builds? option not available
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Brian Surratt | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | Tomcat host running on Linux and Windows, using Firefox and IE as browser. | ||
| Description |
|
For a "trigger build in another configuration" step, the "Propogate variables to dependent builds?" option is not presented on the page. Looking at the demo environment, the option was available in the 1.1.0 (build 1) release As a result, variables from the triggering configuration can not be forwarded to the dependent configuration. In the triggering configuration, I set up the following in the "Override variables" text area: sourceBuildVersion=${build.version} and tried to access the variable in an Ant builder in the dependent configuration as buildVersion=${sourceBuildVersion} the following error occurs in the dependent configuration when it is triggered java.lang.RuntimeException: ognl.NoSuchPropertyException: com.pmease.quickbuild.model.Configuration.sourceBuildVersion Should this work |
| Comments |
| Comment by Brian Surratt [ 03/Jan/07 01:04 PM ] |
|
Please disregard the comments about properties not being propagated. I used the ${var[variableName]} notation in the dependent configuration it worked. Sorry about that. Has the option to propagate variables been removed? Are they always sent with the trigger request? |
| Comment by Robin Shen [ 03/Jan/07 05:44 PM ] |
|
This option has been removed. Instead you will need to explicitely specify variables passed to dependent build as you've already discovered. Regards. Robin |