Indeed it is, how silly of me to miss it!
Thanks!

On Jun 11, 3:40 pm, Ruben Willems <[email protected]> wrote:
> Hi
>
> the property is CCNetRequestSource
> it is listed in the integration properties
>
> with kind regards
> Ruben Willems
>
> On Thu, Jun 11, 2009 at 9:25 PM, Georges<[email protected]> wrote:
>
> > Hello All,
>
> > I would like to schedule a NAnt task build call that will create and
> > publish a snaphost release of a project.
> > This is what my Triggers Block looks like:
>
> > <triggers>
> >                <intervalTrigger name="Subversion" seconds="10" />
> >                <scheduleTrigger time="01:00" buildCondition="ForceBuild"
> > name="publish-snapshot" />
> > </triggers>
>
> > At 1am every day, the "all" NAnt build task will be executed:
>
> > <tasks>
> >      <nant>
> >        <executable>C:\CCNET\MyProject\Working\tools\nant\bin
> > \nant.exe</executable>
> >        <buildFile>C:\CCNET\MyProject\Working\build.xml</buildFile>
> >        <targetList>
> >          <target>all</target>
> >        </targetList>
> >      </nant>
> > </tasks>
>
> > But the actual NAnt target I want the Schedule Trigger to call isn't
> > the "all" target but another one called "publish-snapshot". Is there a
> > way I can map my scheduleTrigger to a specific task in order to
> > achieve this?
>
> > Alternatively, is there a CCNET property I can use to retrieve the
> > value of the scheduleTrigger's name attribute which I could then use
> > in my "all" target to call the "publish-snapshot" target?
>
> > The description of that name attribute says: "The name of the trigger.
> > This name is passed to external tools as a means to identify the
> > trigger that requested the build. (Added in CCNet 1.1)"
> > From what I understand it is possible to retrieve that name attribute
> > value in my NAnt script, but how? It doesn't seem to be set as one of
> > the CCNet integration properties listed here:
> >http://confluence.public.thoughtworks.org/display/CCNET/Integration+P...
>
> > Thanks and regards.
>
> >  - Georges

Reply via email to