|
|
|
[
Permlink
| « Hide
]
Robin Shen [07/Aug/12 12:16 AM]
Now I understand. Unfortunately it is not possible, as variables do not have chance to run at definition time. I suggest to open a second tab to search for desired build with configuration and status to find out desired build, and then define the variable with that build.
I am sorry It seems like I could not explain it well.
I already did use the prompt bean(I checked test prompt bean too). When I run the configuration I get the configuration name and build status then I return the build version. My question is how can I do it during the variable creation and run the configuration without interruption. Thank you... Please refer to method "getTestCaseChoices" in TestSetting class of the example prompt bean. It gets current specified value of testsuite field and calculates the applicable test cases. In your case, you can filter the list of applicable builds with user specified value of configuration and build status.
For example I want to create a variable type that takes configuration name and type of build information and returns the build versions that match the criteria dynamically.
During the adding new variable, one build choice will be selected and stored in the system. I am able to do similar function with bean input. It shows the configurations in the system and type of build(successful, recommended..) and returns the available build versions choices but it happens during the build process which I do not want. I want it to be done during configuration preparation time. Sorry I am still not able to understand this. Can you please describe this with an example?
I want to create a variable that takes some arguments and when the build runs prompt beans class will return choices dynamically then the selected choice will be added into build sequence.
If this is not an option, can I add a new prompt setting class into system that takes arguments and directly returns choices in the edit variable bean? I could not see any extension which lets adding new prompt settings. Currently it is not possible to access this info from within the prompt bean class. Any reason you want to access such info?
|