Hello,

 

We have configured CruiseControl for build scheduling on the build server.
CruiseControl calls the project specific ANT build script. As the build
starts the first thing the build script does is update the projects CVS
directory. The build file contents are as shown below,

 

<project name="build-billgate"

           basedir="gateway/billgate/build">

    <target name="build">

        <!-- Get the latest from CVS -->

        <cvs command="update -P -d" />

        <!-- Call the target that does everything -->

        <ant antfile="build.xml" target="generate.clover.reports"/>

    </target>

</project>

 

All individual projects are under /home/cvs/cruisecontrol/projects

One such project is under /home/cvs/cruisecontrol/projects/gateway/billgate/

The build file above (build-billgate.xml) calls the build file that's in
/home/cvs/cruisecontrol/projects/gateway/billgate/build/build/xml

 

It is observed that the changes committed by developers to the CVS server
are not getting updated on the build server. Because of this the build
fails. I did a manual CVS update of the project directory on the build
server and then ran the build manually using CruiseControl. The updates were
now seen, however the build failed due to certain other reasons (which the
developers will fix). The issue here is the CVS update (updating
files/creating new directories) is not happening properly. As an alternative
I thought of writing a small perl script just for updating the project
directory. This perl script would be called first before the build starts. I
haven't implemented this Perl script yet. But however this would be not a
solution when we already have ANT doing that for us. Could you please help
me out and give me a solution that would fix this issue.

 

We use 'ssh' for CVS authentication.

 

Thanks much.

 

Vivek Payala


DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the 
property of Persistent Systems Pvt. Ltd. It is intended only for the use of the 
individual or entity to which it is addressed. If you are not the intended 
recipient, you are not authorized to read, retain, copy, print, distribute or 
use this message. If you have received this communication in error, please 
notify the sender and delete all copies of this message. Persistent Systems 
Pvt. Ltd. does not accept any liability for virus infected mails.

Reply via email to