PySVN home page: http://pysvn.tigris.org/
PySVN Workbench documentation http://pysvn.tigris.org/docs/WorkBench.html
The kits have been built against SVN 1.7.8 release.
Features of this release:
* Support Subversion 1.7.8
Features of PySVN WorkBench:
* Easy to use working copy management
* Same
PySVN home page: http://pysvn.tigris.org/
The kits have been built against SVN 1.7.8 release
for python 2.6, 2.7, 3.2 and 3.3.
This release include:
* bug fixes for reported issues
* Support SVN 1.7.8
* New Mac installer
Features of PySVN:
* Natural python interface to Subversion
* Supports Sub
On Mon, Dec 31, 2012 at 1:48 PM, Z W wrote:
> Hi All
>
> We are new to SVN.
> We are unsure where to configure in SVN, if needed, while using it
> with Jenkins/Hudson CI tool.
>
> We have a big chained job that runs for about an hour. Chained job
> meaning several jobs combined using downstream co
Guten Tag Z W,
am Montag, 31. Dezember 2012 um 20:48 schrieben Sie:
> Issue: For those files that User C checks in, we like to pick up the
> previous versions of those files, prior to User C's checkouts after
> the job B begins running and not pick up the files versions that User
> B checks in dur
Guten Tag Florian Weimer,
am Dienstag, 1. Januar 2013 um 17:39 schrieben Sie:
> You can specify an explicit revision number when performing the
> checkouts. This way, you can ensure that they are consistent.
But especially in a context of Jenkins and Co. this is not the default
behavior and woul
* Z. W.:
> Issue: For those files that User C checks in, we like to pick up the
> previous versions of those files, prior to User C's checkouts after
> the job B begins running and not pick up the files versions that
> User B checks in during the job B run.
>
> We like to know if there is anything
