forums.parabuildci.org

Dear Slava, Do you see them OK when running a manual checkout? Using CVS client 2.5.03 shows up the same problem from both the command line and parabuild. This problem seems to happen only in the Entries file of the master module hidden CVS directory: maybe because this dir is not a real one but it'...

Dear Slava, We finally traced and solved the issue: it was the CVS/Entries file in the main parabuild checkout dir that was missing ,from time to time , some subdirectories. for example we have: a/u/t/o/MasterModuleName a/u/t/o/MasterModuleName/SubModuleA a/u/t/o/MasterModuleName/SubModuleB a/u/t/o/...

Dear Slava, Is build running on a remote agent or is it running on the build manager? We performed the same tests with the windows build manager and a remote agent. Result is not changing: the dashboard is not able to clean checkoud or update and the cvs process hangs in the task manager (cpu/memory...

Dear Slava, we traced the issue: it was due to our build node CVSNT client 2.5.03 not updating all children modules We found that CVSNT version 2.0.51d available at http://www.pushok.com/soft_download.php?idprogram=2 works OK from the command line but hangs when launched from inside the parabuild pr...

Dear Slava,

all modules are under different CVSROOT.

Anyway performing

cvs update masterModuleName

from the command line is working correctly ie showing the changed files in cvs log.

Regards,
Stefano

Dear Slava, What exactly are the names of the modules entered in Parabuild? Slava I'll try to explain myself better: we are writing just one module name in parabuild CVS repository path. This module is linking several others dependencies modules, also under different CVSROOT's, and each module is de...