On Thu, Jan 27, 2011 at 04:11:35AM -0800, girish hilage wrote:
> find_program(CTEST_SVN_COMMAND NAMES svn)
> set(CTEST_UPDATE_COMMAND "${CTEST_SVN_COMMAND}")
> set(CTEST_UPDATE_OPTIONS "--username <my_svn_username> --password
> <my_svn_password>")
>
> ctest_update(RETURN_VALUE updateRV)
>
> But, when I give 'ctest -S script.cmake', it again asks for the svn
> password eventhough I have hard-coded svn username and password in
> script.cmake.
> My requirement is that, I am setting up a cronjob for nightly builds and I
> do not want it to ask for an svn password.
>
> In the output I can see following lines :
> SetCTestConfigurationFromCMakeVariable:UpdateCommand:CTEST_UPDATE_COMMANDSetCTestConfiguration:UpdateCommand:/usr/bin/svn
> SetCTestConfigurationFromCMakeVariable:UpdateOptions:CTEST_UPDATE_OPTIONSSetCTestConfiguration:UpdateOptions:--username
> <my_svn_username> --password <my_svn_password>
> SetCTestConfigurationFromCMakeVariable:SVNCommand:CTEST_SVN_COMMANDSetCTestConfiguration:SVNCommand:/usr/bin/svn
Your code looks reasonable to me. Have you tried sticking the OPTIONS
directly into CTEST_UPDATE_COMMAND?
You could also let Subversion handle the username/password; it will
cache them if ask it to. The advantage is that you don't have to
hardcode passwords into your build scripts. The disadvantage is this is
something you'll need to take care of for all machines/accounts that do
automated builds.
tyler
_______________________________________________
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
