Parabuild cvs modules issues

Postby **support** » Fri Dec 17, 2010 1:16 pm

I am sorry, but I did not understand your response. What exactly are the names of the modules entered in Parabuild?

Slava

s.perticoni · Postby **s.perticoni** » Mon Dec 20, 2010 2:34 am

Postby **support** » Mon Dec 20, 2010 9:15 am

This makes sense. This problem may have to do with the fact that those are under different CVSROOTs indeed.

Are those modules all under different CVSROOTs?

Slava

Postby **support** » Mon Dec 20, 2010 1:19 pm

We are asking this because Parabuild runs the following command to detect changes:

cvs -d <root> update module
cvs log

Or concern is that that having compound modules with different root may make it impossible to retrieve the modules that are not under <root>. As a result, change detection won't work as well.

Slava

s.perticoni · Postby **s.perticoni** » Tue Dec 21, 2010 9:01 am

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

Postby **support** » Tue Dec 21, 2010 11:09 am

s.perticoni · Postby **s.perticoni** » Thu Dec 23, 2010 8:02 am

Postby **support** » Thu Dec 23, 2010 12:15 pm

s.perticoni · Postby **s.perticoni** » Tue Dec 28, 2010 3:22 am

Postby **support** » Tue Dec 28, 2010 8:41 am

s.perticoni · Postby **s.perticoni** » Tue Dec 28, 2010 10:21 am

Postby **support** » Tue Dec 28, 2010 1:27 pm

forums.parabuildci.org

Parabuild cvs modules issues

Parabuild cvs modules issues

Who is online