I have my system (using AccuRev for SCC) pulling down the config file
in place (in ccnet\server) and it triggers a restart just fine that
way.

On Oct 7, 9:34 pm, Alex <[EMAIL PROTECTED]> wrote:
> So you have to copy it into place to get the changes to pick up as
> well, that is the only way I could do it as well. Simply pulling the
> change down through source control as described in the documentation
> does not clue the service in that the file has changed. I am not sure
> what it checks but it strikes me odd that pulling form source control
> a new file does not get picked up, but pulling it down to another
> location and then copying it over does. However, I had forgotten about
> the validate flag, and that is probably something I should have in
> there. Thanks for the big clue on that one.
>
> On Oct 7, 2:54 pm, "Adam V." <[EMAIL PROTECTED]> wrote:
>
>
>
> > I keep our .configs under source control, and have bootstrap projects
> > that monitor for changes.
> > I'm on CCnet 1.4, so I use ccnet itself to validate XML before
> > redeploying the .config file.
> > I have the server set to watch for .config file changes (which I think
> > is the deafult? I can't remember.)
>
> > I have a project in my .config that watches for changes to the .config
> > itself:
> >         <project name="ccnet-bootstrap">
> >                 
> > <webURL>&dashboard-url;/ccnet-bootstrap/ViewProjectReport.aspx</
> > webURL>
> >                 <workingDirectory>&build-path;\ccnet-bootstrap\working</
> > workingDirectory>
> >                 <artifactDirectory>&build-path;\ccnet-bootstrap\artifacts</
> > artifactDirectory>
> >                 &default-state;
>
> >                 <labeller type="dateLabeller" />
>
> >                 <sourcecontrol type="svn" autoGetSource="true" 
> > timeout="300000"
> > executable='&svn-exe;'>
> >                         
> > <trunkUrl>file:///C:/local_svn_storage/srcweb/srcwebtools/trunk/
> > build</trunkUrl>
> >                 </sourcecontrol>
>
> >                 <tasks>
> >                         <exec executable="python.exe" 
> > buildArgs="update_ccnet_config.py" />
> >                 </tasks>
>
> >         &default-publishers;
> >         </project>
>
> > The build script that gets called is along the lines of (Python
> > script, using a simple "build library"):
>
> > print "= CruiseControl.NET bootstrap ="
> > print "Verifying ccnet config files..."
>
> > with working_folder("ccnet"):
> >     result,output = run(CCNET_EXE+" -validate -config:ccnet-web.config
> > 2>nul")
> >     if result != 0:
> >         sys.stderr.write("error: could not verify \"ccnet-web.config
> > \"\n")
> >         message = output if output else "(unknown error - is the path
> > to ccnet.exe incorrect?)"
> >         sys.stderr.write(message)
> >         sys.exit(99)
>
> > print "Staging new config files..."
> > run("copy ccnet\\*.* "+REAL_CONFIG_PATH)
>
> > print "done."- Hide quoted text -
>
> - Show quoted text -

Reply via email to