<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Yes. I tried giving OPTIONS directly with CTEST_UPDATE_COMMAND but it says "Update command failed".<BR><BR>If I execute "svn update --username <my_svn_username> --password <my_svn_password> --non-interactive" from a simple <SPAN class=yshortcuts id=lw_1296202419_0>shell script</SPAN> (.sh file),<BR><BR>then it works fine without prompting for a password.<BR><BR>Does that mean 'svn update' with svn credentials do not work as expected in the ctest script?<BR>Is, first storing the SVN credentials on a machine executing the cronjob, the only solution? </DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Girish<BR><BR>--- On <B>Thu, 1/27/11, Tyler Roscoe <I><tyler@cryptio.net></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>From: Tyler Roscoe <tyler@cryptio.net><BR>Subject: Re: [CMake] using svn credentials inside ctest script<BR>To: "girish hilage" <girish_hilage@yahoo.com><BR>Cc: cmake@cmake.org<BR>Date: Thursday, January 27, 2011, 4:42 PM<BR><BR>
<DIV class=plainMail>On Thu, Jan 27, 2011 at 08:40:14AM -0800, Tyler Roscoe wrote:<BR>> On Thu, Jan 27, 2011 at 04:11:35AM -0800, girish hilage wrote:<BR>> > find_program(CTEST_SVN_COMMAND NAMES svn)<BR>> > set(CTEST_UPDATE_COMMAND "${CTEST_SVN_COMMAND}")<BR>> > set(CTEST_UPDATE_OPTIONS "--username <my_svn_username> --password <my_svn_password>")<BR>> > <BR>> > ctest_update(RETURN_VALUE updateRV)<BR>> > <BR>> > 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.<BR>> > 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.<BR>> > <BR>> > In the output I can see following lines :<BR>> >
SetCTestConfigurationFromCMakeVariable:UpdateCommand:CTEST_UPDATE_COMMANDSetCTestConfiguration:UpdateCommand:/usr/bin/svn<BR>> > SetCTestConfigurationFromCMakeVariable:UpdateOptions:CTEST_UPDATE_OPTIONSSetCTestConfiguration:UpdateOptions:--username <my_svn_username> --password <my_svn_password><BR>> > SetCTestConfigurationFromCMakeVariable:SVNCommand:CTEST_SVN_COMMANDSetCTestConfiguration:SVNCommand:/usr/bin/svn<BR>> <BR>> Your code looks reasonable to me. Have you tried sticking the OPTIONS<BR>> directly into CTEST_UPDATE_COMMAND?<BR>> <BR>> You could also let Subversion handle the username/password; it will<BR>> cache them if ask it to. The advantage is that you don't have to<BR>> hardcode passwords into your build scripts. The disadvantage is this is<BR>> something you'll need to take care of for all machines/accounts that do<BR>> automated builds.<BR><BR>One other thing that I had to discover myself
and which I haven't<BR>noticed in any CTest documentation:<BR><BR># 'update' and '--non-interactive' are automatically added to<BR># CTEST_UPDATE_COMMAND by CTest.<BR><BR>So maybe --non-interactive is interfering with --username/--password? It<BR>shouldn't but it's another thing to test.<BR><BR>tyler<BR></DIV></BLOCKQUOTE></td></tr></table><br>