My company has a continuous integration server running ccnet  Version : 
1.6.7981.1

If successful, the main build project will kick off two other projects. 
 Unfortunately the other two projects' next build time is being set too far 
in the future that they won't run.
Most of the time, the sub-project's "next build time" is correct and 
everything works.
But after a few days of working correctly the "next build time" will be set 
up to a couple of weeks into the future.

If I make a small change in a ccnet config and dynamically refresh ccnet, 
the "next build time" will be correctly set and they'll be synchronized 
with the ci project.
Or if I force the sub project the date will correct itself.

I have scanned the user group for a similar bug but could not find one.
I have also looked in all issues.

The trigger configuration for both projects
    <triggers>
        <!-- Kicks off a build when Client12 is successful. -->
        <projectTrigger project="Client12" />
    </triggers>

The system is running on Windows Server 2008.


Andrew

Reply via email to