Oh man, it helps when you're able to read the docs. Obviously I'm not.
It's working now.

Sorry and thanks a lot,

Markus

On 15 Mrz., 21:52, "Craig Sutherland" <[email protected]>
wrote:
> Hi Markus,
>
> I've found the problem - the cruiseServerControl item is a task, so it needs
> to be in one of the tasks blocks (e.g. prebuild, tasks or publishers). For
> example, here is your current project definition:
> <project name="_Start_All_Projects" category="Sonstige" queue="Allgemein">
>         <webURL>http://buildserver/ccnet/</webURL>
>         <workingDirectory>C:\AutomatedBuild</workingDirectory>
>
> <artifactDirectory>C:\AutomatedBuild\Output\Sonstige\_Stop_All_Projects</ar­t
> ifactDirectory>
>         <state type="state" directory="C:\AutomatedBuild\Output" />
>         <!-- A force build of this project sends a START command to all
> projects. -->
>         <cruiseServerControl>
>                 <actions>
>                         <controlAction>
>                                 <project>*</project>
>                                 <type>StartProject</type>
>                         </controlAction>
>                 </actions>
>         </cruiseServerControl>
> </project>
>
> If you can it to:
> <project name="_Start_All_Projects" category="Sonstige" queue="Allgemein">
>         <webURL>http://buildserver/ccnet/</webURL>
>         <workingDirectory>C:\AutomatedBuild</workingDirectory>
>
> <artifactDirectory>C:\AutomatedBuild\Output\Sonstige\_Stop_All_Projects</ar­t
> ifactDirectory>
>         <state type="state" directory="C:\AutomatedBuild\Output" />
>         <!-- A force build of this project sends a START command to all
> projects. -->
>         <tasks>
>                 <cruiseServerControl>
>                         <actions>
>                                 <controlAction>
>                                         <project>*</project>
>                                         <type>StartProject</type>
>                                 </controlAction>
>                         </actions>
>                 </cruiseServerControl>
>         </tasks>
> </project>
>
> It will work.
>
> Craig
>
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
>
> Behalf Of MarkusW
> Sent: Monday, 15 March 2010 3:14 p.m.
> To: ccnet-user
> Subject: [ccnet-user] Re: Stop all projets at once
>
> I'm running the latest version 1.5.6960.1 from ccnetlive.
>
> I tried pasting the complete error log but then google won't accept the
> message. I'll send it to your mail address.
>
> Markus
>
> On 15 Mrz., 02:30, "Craig Sutherland" <[email protected]>
> wrote:
> > It is not recognising the task. What version of CC.NET are you running?
>
> > Craig
>
> > -----Original Message-----
> > From: [email protected] [mailto:[email protected]]
> > On
>
> > Behalf Of MarkusW
> > Sent: Monday, 15 March 2010 2:14 p.m.
> > To: ccnet-user
> > Subject: [ccnet-user] Re: Stop all projets at once
>
> > > 1. Yes, it looks complete.
>
> > Obviously it isn't. As the _Stop_All_Projects/_Start_All_Projects
> > projects were not recognized i ran ccnet.exe. Unfortunately the output
> > isn't of any help to me.
>
> > [CCNet Server:ERROR] Exception: Unused node detected:
> > <cruiseServerControl><acti
> > ons><controlAction><project>*</project><type>StopProject</type></
> > controlAction><
> > /actions></cruiseServerControl>
>
> > What did I do wrong?
>
> > TIA,
>
> > Markus
>
> > On 13 Mrz., 10:04, "Craig & Sammi Sutherland"
> > <[email protected]> wrote:
> > > Hi Markus,
>
> > > Answers to your questions:
> > > 1. Yes, it looks complete.
>
> > > 2. It would send multiple stop commands (since the task does not
> > > check the current status). However, when the server gets these
> > > commands, it would ignore them, since the projects are already
> > > stopped (the single exception will the stop-all project, since doing
> > > a force build automatically re-starts
> > > it.)
>
> > > 3. This is similar to #2 - since the projects are already started,
> > > it would ignore the commands.
>
> > > 4. You shouldn't. The start/stop commands are the same as pressing
> > > the start/stop button on the dashboard - it will not perform a build
> > > (unless the project has been configured to build on start-up.)
>
> > > Craig
>
> > > -----Original Message-----
> > > From: [email protected]
> > > [mailto:[email protected]]
> > > On
>
> > > Behalf Of MarkusW
> > > Sent: Saturday, 13 March 2010 2:21 a.m.
> > > To: ccnet-user
> > > Subject: [ccnet-user] Re: Stop all projets at once
>
> > > Hi Craig,
>
> > > looks like you just implemented exactly what I was looking for. :-)
> > > Now a few questioons came up.
>
> > > 1. I'd use this XML markup for a "stop all" project. Is it correct
> > > and complete?
>
> > >         <project name="_Stop_All_Projects" category="Others"
> > > queue="General">
> > >                 <webURL>http://buildserver/ccnet/</webURL>
> > >                
> > > <workingDirectory>C:\AutomatedBuild</workingDirectory>
> > >                 <artifactDirectory>C:\AutomatedBuild\Output\Others
> > > \_Stop_All_Projects</artifactDirectory>
> > >                 <state type="state"
> > > directory="C:\AutomatedBuild\Output" />
> > >                 <!-- A force build of this project sends a STOP
> > > command to all projects. -->
> > >                 <cruiseServerControl>
> > >                         <actions>
> > >                                 <controlAction>
> > >                                         <project>*</project>
> > >                                         <type>StopProject</type>
> > >                                 </controlAction>
> > >                         </actions>
> > >                 </cruiseServerControl>
> > >         </project>
>
> > > 2. What happens when a user hits the [Force] button of the "stop all"
> > > project on the web dashboard several times in a row?
>
> > > 3. Can something bad happen when a user hits the [Force] button of
> > > the "start all" project on the web dashboard while all projects are
> > > running?
>
> > > 4. Most of our projects are running an interval trigger. A few are
> > > "force build only". Will I run into problems?
>
> > > TIA,
>
> > > Markus Winhard
>
> > > On 12 Mrz., 09:07, "Craig & Sammi Sutherland"
> > > <[email protected]> wrote:
> > > > Hi Markus,
>
> > > > This is a good idea and one that is reasonably easy to implement -
> > > > so I
> > > have
> > > > added it to the latest build.
>
> > > > As an example, you can now use the following task to stop all the
> > > > projects on a server:
> > > > <cruiseServerControl>
> > > >   <actions>
> > > >     <controlAction>
> > > >       <project>*</project>
> > > >       <type>StopProject</type>
> > > >     </controlAction>
> > > >   </actions>
> > > > </cruiseServerControl>
>
> > > > The project uses the standard Windows wildcard mappings - i.e. * and
> ?.
> > > You
> > > > can use these to build a "pattern" of projects to apply the
> > > > commands to (e.g. "*-Build", "Project?", etc.)
>
> > > > If you want a client-side app, the options are using something
> > > > like FastForward.NET (as suggested by Christophe - available
> > > fromhttp://www.ohloh.net/p/FastForwardNET/download) or building your
> > > own custom
> > > > program (as suggested by Ruben).
>
> > > > One thing to note with these (and any other approach for sending a
> > > > stop command), the stop command will change the project state to
> > > > Stopping. If there is a build in progress it will remain in this
> > > > state until the build has finished and then transition to Stopped.
> > > > If there is no build it will change immediately to Stopped. So if
> > > > the stop command does not work immediately, this is probably why.
>
> > > > Hope this helps,
>
> > > > Craig
>
> > > > -----Original Message-----
> > > > From: [email protected]
> > > > [mailto:[email protected]] On
>
> > > > Behalf Of MarkusW
> > > > Sent: Friday, 12 March 2010 7:11 a.m.
> > > > To: ccnet-user
> > > > Subject: [ccnet-user] Re: Stop all projets at once
>
> > > > What about using a star for the project name or an empty project
> > > > name?
> > > > e.g. <controlAction type="StopProject" project="*" /> Will this
> > > > automatically stop all projects?
>
> > > > Markus
>
> > > > On 11 Mrz., 10:32, JayFleming <[email protected]>
> > > > wrote:
> > > > > Hi Markus,
>
> > > > > If you're on version 1.5+ you could have a control project that
> > > > > ran multiple CruiseServerControl tasks to shut down all the
> > > > > projects from one
>
> clickhttp://confluence.public.thoughtworks.org/display/CCNET/CruiseServer+..
> > > > ..
>
> > > > > There is the pain of setting up the 50+ tasks initially, but it
> > > > > could be more practical in the end...the control project could
> > > > > just be scheduled to shut everything down 5 minutes before your
> > > > > source VM is taken offline.
>
> > > > > Cheers,
> > > > > Jay- Zitierten Text ausblenden -
>
> > > > - Zitierten Text anzeigen -- Zitierten Text ausblenden -
>
> > > - Zitierten Text anzeigen-- Zitierten Text ausblenden -
>
> > - Zitierten Text anzeigen-- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -

Reply via email to