RE: [ccnet-user] Using named values in condition blocks

[Andrew Hayes]

I'm still struggling with this; any clues anyone could suggest would be very
helpful...

Thanks
Andrew
-----Original Message-----
From: ccnet-user@googlegroups.com [mailto:ccnet-u...@googlegroups.com] On
Behalf Of andrew
Sent: Friday, April 16, 2010 9:12 AM
To: ccnet-user
Subject: [ccnet-user] Using named values in condition blocks

We are running two basic types of builds: Normal and Nightly "Big"
builds. Normal builds on changes to the depot; and doesn't build some
of the really big projects we have. Nightly builds everything; and so
we restrict that to run once a day; starting at 1am.

Our trigger has this block:
             <parameterTrigger>
                    <trigger type="scheduleTrigger" time="01:00"
buildCondition="ForceBuild" name="Nightly post-scorch build" />
                    <parameters>
                        <namedValue name="isNightlyBuild" value="yes"/
>
                    </parameters>
                </parameterTrigger>

We also want users, when forcing a build, to have the option of
running a nightly build as well; so we are using parameters for that.
Our project definition has this block:

           <parameters>
                <selectParameter>
                    <name>isNightlyBuild</name>
                    <allowedValues>
                        <value name="Nightly Big-Build">yes</value>
                        <value name="Normal Build">no</value>
                    </allowedValues>
                    <display>Nightly BIG Build?</display>
                    <description>removed for brevity...</description>
                    <default>Normal Build</default>
                    <required>false</required>
                </selectParameter>
            </parameters>

To scope what is/is not built we installed the Conditional plugin.

To test what is happening we added this line to the top of our tasks
block:
                <!-- Output the build type to the log -->
                <conditional description="Log state of isNightlyBuild
flag">
                    <conditions>
                        <compareCondition value1="$[isNightlyBuild]"
value2="yes" evaluation="equal" ignoreCase="true"/>
                    </conditions>
                    <tasks>
                        <commentTask message="isNightlybuild is true"/
>
                    </tasks>
                    <elseTasks>
                        <commentTask message="isNightlybuild is false"/
>
                    </elseTasks>
                </conditional>

The problem is that if you start the build with a force, and set
isNightlyBuild to Yes; it works (logs as you would expect); but the
NIGHTLY trigger at 1am does not seem to set this flag correctly.

Any suggestions?

Thanks
Andrew


-- 
Subscription settings:
http://groups.google.com/group/ccnet-user/subscribe?hl=en

smime.p7s
Description: S/MIME cryptographic signature