Hi Beth, Your configuration is correct - there was a bug in the code which was preventing the parameters from being passed to publishers (or prebuild tasks). Since this was reasonably simple, I have put in a fix for the bug - when CCNetLive finishes building it should be ok.
This is one of the new features that was added for 1.5, hence the reason for some of the issues. So sorry for the difficulties and thanks for sharing your issues with us. Also, on a final note, I'm away on holiday for the next three weeks, so I won't be able to look into the other issue with the $[...] syntax and targetList until I get back. Craig ________________________________ From: Beth Hechanova <[email protected]> To: [email protected] Sent: Fri, October 23, 2009 5:49:54 AM Subject: [ccnet-user] Using Dynamic Parameters in both nant task and publisher task Sorry, I am still struggled with trying to use Dynamic Parameters. I have a Select Parameter set up to allow choice of build type on the dashboard. I have a nant task that passes the selected buildtype to my build file. I also have a nant task in my Publish task that is also trying to pass the selected build type to a different nant script. This one does not pass the selected build type through. I see the documentation states: “Parameters are used at the task/publisher level. They cannot be used in any other project elements. Using parameters can be done in one of two ways: configuration definition or implied replacement. Note: Not all tasks/publishers allow the use of dynamic parameters. To be able to use the parameters a task must expose a dynamicValues element...” Should I be able to pass the selected buildtype in both the nant and publish tasks to two different nant scripts? Here’s what I have: <parameters> <selectParametername="buildType"> <description>The type of build to perform</description> <allowedValues> <valuename="Development">development</value> <valuename="Integration">integration</value> <valuename="Release">release</value> </allowedValues> </selectParameter> </parameters> <snip…> <tasks> <nant> <executable>C:\Program Files\nant\bin\nant.exe</executable> <baseDirectory>C:/BuildArea/IMSRma-New</baseDirectory> <nologo>false</nologo> <buildFile>C:\Projects\CCnet\IMSRma\workingDirectory\src\IMSRma-new.build</buildFile> <targetList> <target>build.application</target> </targetList> <buildTimeoutSeconds>1200</buildTimeoutSeconds> <dynamicValues> <directValue> <default>development</default> <parameter>buildType</parameter> <property>targetList[0]</property> </directValue> </dynamicValues> </nant> </tasks> <publishers> <snip…> <nant> <executable>C:\Program Files\nant\bin\nant.exe</executable> <nologo>false</nologo> <baseDirectory>C:/BuildArea/IMSRma-New</baseDirectory> <buildFile>C:\Projects\CCnet\IMSRma\workingDirectory\src\IMSRma.publish.build</buildFile> <buildTimeoutSeconds>300</buildTimeoutSeconds> <targetList> <target>test.publish</target> </targetList> <dynamicValues> <directValue> <default>development</default> <parameter>buildType</parameter> <property>targetList[0]</property> </directValue> </dynamicValues> </nant> </publishers> As I said, the selection is passed to the IMSRma-new.build script as expected. (On an unrelated note, the target ‘build.application’ in the targetList is not called). So I thought I could use the same in my publisher block. However only the default ‘development’ is passed to the IMSRma.publish.build script. Is that the expected behavior? Or is there some way I can get the selection passed to my publish script too? Thanks, Beth This email and any files transmitted with it are confidential & proprietary to Systems and Software Enterprises, Inc. (dba IMS). This information is intended solely for the use of the individual or entity to which it is addressed. Access or transmittal of the information contained in this e-mail, in full or in part, to any other organization or persons is not authorized.
