On Thu, Apr 4, 2013 at 9:11 AM, weirpenguin <weirpeng...@gmail.com> wrote:
> As I am really new to Jenkins and our company basically use Tortoise as the
> SVN client, we started with the idea of using Tortoise to update SVN. But I
> agree that some Jenkins built-in function could be some better choice and
> will start to look at it.
In a typical 'CI' setup you would use whatever desktop tools you like
to commit your changes to subversion, and configure jenkins to poll
the subversion server periodically at the project URL for each job.
When it notices a change, it will check out/update its own copy with
its internal subversion client and run the job for you.
--
Les Mikesell
lesmikes...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
