On 25 June 2013 18:07, Andrew Stitcher <astitc...@redhat.com> wrote: > On Tue, 2013-06-25 at 15:41 +0100, Robbie Gemmell wrote: > > The Jenkins job to run the Java client tests against the C++ broker has > > been failing since this commit last week. It seems to be having trouble > > trying to copy a file to its own location. > > > > > https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Cpp-Test/1431/ > > > > Is this an issue with the Jenkins job, or the build process? > > Hmm, the jenkins job appears to be building in place, which is not what > we recommend for the C++ build. Having said that it is supposed to work. > > The easiest fix (given that we are removing the autotools build soon and > so don't want to spend lots of time on it) would be to move to a build > with a separate build directory. > > Something like instead of: > > cd qpid/cpp > ./bootstrap > ./configure > make > > Do > > cd qpid/cpp > ./bootstrap > cd .. > mkdir BLD > cd BLD > ../cpp/configure > make > > I think the 'cpp[-*]' Java test profiles actually depend on the in-tree build in order to know where to find the broker. I'll try to take a look at them later and see about updating them.
> > > (The job is still using the Autotools build, as we have yet to try > swapping > > it to CMake and requesting installation of any necessary packages on the > > Jenkins nodes...anyone actually working on C++ bits is of course also > > welcome to volunteer :P) > > We will need to shift to cmake soon, what is involved in doing this? I'm > happy to help here. > That would be great. You would need access to the Jenkins nodes, which Carl can grant you on request. After that it would just be a case of changing the script the job executes, trying it, and emailing bui...@apache.org if necessary to request additional packages on the nodes to get it working. Since Proton is already being built on them it may be the case that the necessary packages are already installed. Robbie
