Run Personal Build with Subversion

Hello, I'm using ssh+svn access to my subversion repository. Is there any
way I can make my personal builds use an ssh key file for authentication
so I can commit after a successful build?

Many thanks,
Pablo
--


If I may venture my own definition of a folk song, I should call
it "an individual flowering on a common stem."
-- Ralph Vaughan Williams

Pablo Montilla
www.odyssey.com.uy

8 comments

Hello,

It should work if svn command line client remembers you password.

VS addin can add --username and --password command line arguments to the
calls to svn cli.
To switch it on, please open Subversion tab on Remote Run dialog.

Thanks!

--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello, I'm using ssh+svn access to my subversion repository. Is there
any way I can make my personal builds use an ssh key file for
authentication so I can commit after a successful build?

Many thanks,
Pablo
Pablo Montilla
www.odyssey.com.uy



0

On Fri, 11 Jan 2008 13:47:00 -0200, Eugene Petrenko
<eugene.petrenko@jetbrains.com> wrote:

Hello,

>

It should work if svn command line client remembers you password.
VS addin can add --username and --password command line arguments to
the calls to svn cli.
To switch it on, please open Subversion tab on Remote Run dialog.

>

Thanks!

>
I did as you told me, and I got this error message:

Subversion failed with message svn: Commit failed (details follow):
svn: Can't create tunnel: The system cannot find the file specified..

Svn has exited with code '1'.

SvnCommitCommand failed


I'm using TortoiseSVN on the client, and have no problems committing. The
server is configured with a key file to get the sources via ssh, and that
works too...how can I do the same for the personal build? Do I need to
configure svn (the command line version) somehow?

Thanks,
Pablo

--


There is only one way to kill capitalism - by taxes, taxes, and more taxes.
-- Karl Marx (1818-1883)

Pablo Montilla
www.odyssey.com.uy

0

Hello Pablo,

VS plugin tries to commit files using 'svn commit ]]> --username ???
--password -m ???'
Is that enough to commit in your case?

Could you please try to commit some file using svn cli? What commandline
is used?

Thanks! And sorry for delay.
--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

On Fri, 11 Jan 2008 13:47:00 -0200, Eugene Petrenko
<eugene.petrenko@jetbrains.com> wrote:

>> Hello,
>>
>> It should work if svn command line client remembers you password.
>> VS addin can add --username and --password command line arguments to
>> the calls to svn cli.
>> To switch it on, please open Subversion tab on Remote Run dialog.
>> Thanks!
>>

I did as you told me, and I got this error message:

Subversion failed with message svn: Commit failed (details follow):
svn: Can't create tunnel: The system cannot find the file specified..

Svn has exited with code '1'.

SvnCommitCommand failed

I'm using TortoiseSVN on the client, and have no problems committing.
The server is configured with a key file to get the sources via ssh,
and that works too...how can I do the same for the personal build? Do
I need to configure svn (the command line version) somehow?

Thanks,
Pablo
Pablo Montilla
www.odyssey.com.uy



0

On Wed, 23 Jan 2008 13:13:27 -0200, Eugene Petrenko
<eugene.petrenko@jetbrains.com> wrote:

Hello Pablo,

>

VS plugin tries to commit files using 'svn commit <files> --username
??? --password -m ???'
Is that enough to commit in your case?

>

Could you please try to commit some file using svn cli? What
commandline is used?

>

Thanks! And sorry for delay.


It isn't enough. I'm not using user name and password, I'm using a private
key file to authenticate with my svn server.

I have configured putty to use the client certificate with connections to
my server wich in turn is used by TortoiseSVN to connect and interact with
my server. The same is true for my TeamCity server configuration, where
I'm using a key file so the server can retrieve files from subversion.

I need that to be an option for Personal Builds to be useful.

Thank you very much,
Pablo

--


Would that my hand were as swift as my tongue.
-- Alfieri

Pablo Montilla
www.odyssey.com.uy

0

Hello,

Could you please show more details about how to configure it.
VS plugin simpy tries to call svn.exe commit. Is that enough or how
should it be called from command line. I can fix the way commandline is
being created.

I think you will have to set up putty for svn.exe too. You may select in
the
commit dialog's tab 'Subversion' to not to provide password what calling
svn.exe or
you may select the path where to get svn.exe


Please file Jira request on the issue

Thanks.
--
Eugene Petrenko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

On Wed, 23 Jan 2008 13:13:27 -0200, Eugene Petrenko
<eugene.petrenko@jetbrains.com> wrote:

>> Hello Pablo,
>>
>> VS plugin tries to commit files using 'svn commit --username >> ??? --password -m ???' >> Is that enough to commit in your case? >> Could you please try to commit some file using svn cli? What >> commandline is used? >> >> Thanks! And sorry for delay. >>]]>

It isn't enough. I'm not using user name and password, I'm using a
private key file to authenticate with my svn server.

I have configured putty to use the client certificate with connections
to my server wich in turn is used by TortoiseSVN to connect and
interact with my server. The same is true for my TeamCity server
configuration, where I'm using a key file so the server can retrieve
files from subversion.

I need that to be an option for Personal Builds to be useful.

Thank you very much,
Pablo
Pablo Montilla
www.odyssey.com.uy



0

On Thu, 24 Jan 2008 11:54:24 -0200, Eugene Petrenko
<eugene.petrenko@jetbrains.com> wrote:

I think you will have to set up putty for svn.exe too. You may select
in the commit dialog's tab 'Subversion' to not to provide password


Umm...looking around I found this article:
http://agateau.wordpress.com/2007/07/03/windows-svnssh-and-the-subversion-command-line-client/

I've configured svn to work from the command line now, and I can commit
giving a username only. I'll try the Personal Build and see if that works
too.

Thanks,
Pablo

--


Beverly: "Do you remember anything more about yourself?"
MacDuff: "No, I'm sorry, Doctor."
Beverly: "Back to square one."
-- "Conundrum", Stardate 45494.2

Pablo Montilla
www.odyssey.com.uy

0

As it's usually the case, the problem was mine. It worked correctly now.

I would change something tough. If the personal build runs correctly, and
the changes are committed, isn't it a waste that we run the build again? I
understand that the project is built again because there are changes in
the server, but there sure must be a way to make the personal build the
last successful build.

Many thanks,
Pablo
--


Written by a highly caffeinated mammal.
-- Disclaimer

Pablo Montilla
www.odyssey.com.uy

0

Pablo,

We have alike issue filed already: http://www.jetbrains.net/jira/browse/TW-990
Please vote/watch/comment it.

I doubt we will approach to that any time soon, but anyway, thank you for sharing your thoughts!

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Please sign in to leave a comment.