Hi, I've been having a problem with with just one project out a dozen that use triggers (mostly urlTriggers) for continuous integration. First I need to describe the overall design.
I'm using CCNET 1.4.4.75. I'm using Accurev SourceControl block, and here is what it looks like: <sourcecontrol type='accurev'> <autoGetSource>false</autoGetSource> <executable>accurev.exe</executable> <!-- <homeDir>.</homeDir> --> <labelOnSuccess>false</labelOnSuccess> <login>true</login> <password></password> <principal>buildTwo</principal> <timeout units='minutes'>10</timeout> <workspace>D:\Projects\SB2\MiddleTier</workspace> </sourcecontrol>" > In accurev I'm using a post-promote trigger (perl script). Part of that script is that it writes an XML file to a Virtual Directory in IIS on the build server. It is this url that the urlTrigger checks. Here the trigger block: <triggers> <!-- url Trigger --> <!--<intervalTrigger name="continuous" initialSeconds="60" seconds="60" buildCondition="IfModificationExists" /> --> <urlTrigger url="http://server031/CCTriggers/ MiddleTier_&ProjectID;.xml" seconds="60" /> </triggers> As you can see I've tried both urlTrigger and interval trigger, so much educated guess is that it's a problem detecting changes in source control. I'm a developer and by no means a build or source control expert, but I've diffed all the files against the 11 other projects that are running with the exact same design as above. This is the ONLY project that won't trigger a build. Another clue is that it DOES work if the Accurev workspace for the build user specified in the above SC block is backed to the correct stream. This tells me two more things. 1) Accurev is finding the correct stream based on the workspace directory and 2) it even more strongly points to problems with the source control linkage. This is an undesirable dependency because that workspace could be moved at any time. I've spent hours diffing files, searching for a fatfinger, looking at logs. Now there isn't really a lot of log files to look at because again, the build never starts. So the nant scripts themselves really don't play a part. Can someone suggest a place to look or any theories about what could possibly be going wrong with this particular project, when it appears to be so similar to many other working projects? Perhaps someone can suggest a log to look at or a way to log the source control interaction with CCNet in a way that I could get some clues. Thanks for any help you can give. I'm really at a loss and sort of desperate at this point. Regards, Adam -- To unsubscribe, reply using "remove me" as the subject.
