[CMake] find_package(Subversion) fails when run by an automated Jenkins build

[Massaro Alessio]

Switching the Jenkins node services to run under the correct build service AD domain account fixed the problem...I think. I did the switch to fix some other unrelated problem, then went back to address this one, and found that it had fixed itself.

Before fixing itself, the Jenkins node services were running under the built-in system account.

Thanks very much for the feedback!


-----Original Message-----
From: Eric Noulard [mailto:eric.noulard at gmail.com] 
Sent: 29 February 2012 18:32
To: Massaro Alessio
Cc: cmake at cmake.org
Subject: Re: [CMake] find_package(Subversion) fails when run by an automated Jenkins build

2012/2/29 Massaro Alessio <Alessio.Massaro at mediobanca.co.uk>:
> Hi there,
>
>
>
> Awkward behaviour:
>
>
>
> My CMakeLists.txt do a find_package(Subversion)
>
>
>
> Now, I have a Jenkins build server running under domain user XYZ
>
> The Jenkins CMake plugin tells me it's trying to do the following:
>
>
>
>          "c:\Program Files\CMake 2.8\bin\cmake.exe"  -G "Visual Studio 
> 9 2008"
>
>                  -DCMAKE_BUILD_TYPE=Release 
> "D:\path\to\where\jenkins\puts\mysource"
>
>
>
> And fails with
>
>
>
>          -- Could NOT find Subversion (missing:  
> Subversion_SVN_EXECUTABLE)
>
>
>
> But if I logon to that very same server with that very same domain 
> user, check-out the code from svn elsewhere on the server disk and run 
> the above command (adjusting for the different path to the source), 
> then the find_package will work just fine.


> Does anyone have a clue on what the problem might be?
> What might be causing the difference in behaviour?


May be the path is set to a different value in the "Jenkins context".
You could try to make your CMakeLists.txt display the content of the PATH variable with something like;

MESSAGE("PATH=$ENV{PATH}")

that way you'll see if something is different

--
Erk
Le gouvernement représentatif n'est pas la démocratie -- http://www.le-message.org