triggering svn update on remote machine
postm...@tigris.org
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=980953
To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].
Simon Large
> I've got a problem with triggering update on remote machine. I've got bunch of svn clients and few users who request ability to trigger svn update on client machines. All machines have tortoisesvn installed. Doing that by hand, machine by machine, is out of question - there are tens of client machines. Also doing that at specific time interval is not acceptable - client machines are not to be updated unless forced by user, when forced must run svn update at once and user must be able to check whether there were problems or not easy way. Everything on windows. Any suggestions? I don't feel like spending time on writing custom daemon for that. There must be an easy way.
TortoiseSVN is a GUI app, so it intended for interactive use. If you
want to do some sort of scripted update then you should be using the
subversion command line client instead. As for how to trigger such a
script remotely, that is an exercise for you. In most places being
able to execute code remotely without the local user being involved
would be considered a security flaw, so it is not a feature you are
going to see built into subversion.
Simon
--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=981040
Kurt Pruenner
> TortoiseSVN is a GUI app, so it intended for interactive use. If you
> want to do some sort of scripted update then you should be using the
> subversion command line client instead. As for how to trigger such a
> script remotely, that is an exercise for you. In most places being
> able to execute code remotely without the local user being involved
> would be considered a security flaw, so it is not a feature you are
> going to see built into subversion.
Since this request comes up every so often - maybe they just want to use
TSVN because it pops up a nice progress dialog with the status messages
the user can check and dismiss instead of just dumping all output into a
console window?
Even though I personally don't need that I don't see why that's not
something that should be supported instead of those users somehow having
to reinvent the wheel just to get something similar done. So why not
just add another command line option to TortoiseProc to run a command
directly instead of opening the corresponding dialog?
--
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
.......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
np: Swod - Patinage (Sekunden)
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=981105
Bob Archer
I am pretty sure that CI Factory does this.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessage
Id=981105
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=981188
Kurt Pruenner
> You can use TSVN from the command line... but you will get the dialogs.
> I am pretty sure that CI Factory does this.
I know - that's why I asked for an option to skip the dialogs, when you
can specify values for almost everything in the dialogs already...
--
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
.......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
np: Boy Robot - Old Habits Die Hard (Glamorizing Corporate Lifestyle)
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=981190
Bob Archer
line client? Both TSVN and SVN clients can be on the machine. As long as
they are the same root versions (1.5.x and 1.5.x for example) so WC's
will work with both clients.
-----Original Message-----
From: Kurt Pruenner [mailto:le...@gmx.at]
Sent: Monday, December 08, 2008 11:28 AM
To: us...@tortoisesvn.tigris.org
Subject: Re: triggering svn update on remote machine
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessage
Id=981190
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=981191
Kurt Pruenner
> I see. If you don't want the dialogs... why not just use the svn command
> line client? Both TSVN and SVN clients can be on the machine. As long as
> they are the same root versions (1.5.x and 1.5.x for example) so WC's
> will work with both clients.
Personally, I'm not even interested in calling TSVN from the command
lien, it's just that it's come up so often that I just had to comment on it.
And yes, you can use the SVN command line client, but you won't get the
pretty (and way more useful) TSVN status dialog that shows the progress
of the operation to the user, especially in case there is an error.
The SVN command line is fine if you just want to script something, but
if you want the user to be aware that something SVN related is in
progress TSVN's status dialog way trumps a boring old console window...
--
Kurt Bernhard Pruenner --- Haendelstrasse 17 --- 4020 Linz --- Austria
.......It might be written "Mindfuck", but it's spelt "L-A-I-N".......
np: Benni Hemm Hemm - Abbastúfur (Kajak)
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=981200