It became a top-level Apache project on February 17, 2010. In November 2009, Subversion was accepted into Apache Incubator: this marked the beginning of the process to become a standard top-level Apache project. By 2001, Subversion had advanced sufficiently to host its own source code, and in February 2004, version 1.0 was released. History ĬollabNet founded the Subversion project in 2000 as an effort to write an open-source version-control system which operated much like CVS but which fixed the bugs and supplied some features missing in CVS. in 2000, and is now a top-level Apache project being built and used by a global community of contributors. CodePlex was previously a common host for Subversion repositories. The open source community has used Subversion widely: for example, in projects such as Apache Software Foundation, FreeBSD, SourceForge, and from 2006 to 2019, GCC. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. In this case, the repository is readable by anyone from the server computer (also true for the file:// protocol).Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system distributed as open source under the Apache License. With this protocol, if the repository resides on the server's local drive then the following can be used: svnserve -d -listen-host 127.0.0.1. The svn:// protocol is faster, but it requires start-up of the svnserve server (part of the Subversion installation). This is the simplest alternative, as nothing other than the repoSystem property needs to be configured. The file:// protocol can be used when the SVN repository resides on the server computer's local drive. If this property is not set, the system user uses the normal access URL as specified by the repo system property.Įither of two protocols can be used when specifying the URL value in the repoSystem property: The system property repoSystem can be used to provide an alternative repository URL to be used for read-only access by the system user. On Polarion installations with large amounts of content, there can be significant performance benefits from setting up alternate access to the Subversion repository for the system user, especially for system indexing/reindexing. The following external resource may be helpful: Review your cache memory to be sure the assigned cache for SVN will not consume too much memory when parallel connections are made.Īssign at least 128 MB cache allocation via SVNInMemor圜acheSize 131072 for Apache.Īssign at least 128 MB cache allocation via -M 128 for svnserve.īecause a process is spawned for each connection and there might be dozens of such connections with highly concurrent use of Polarion, the total amount of memory occupied by svnserve may be high. For example, given a recommend cache of at least 128 MB as svnserve cache, and if there are 10 parallel requests to SVN at the same time, at that moment the processes consume 10 * 128 MB memory, or 1280 MB. Make sure you have enough memory for recommended cache size multiplied by the anticipated number of parallel connections to SVN. By default, both Apache and svnserve use new processes to serve incoming connections, so the allocated cache is specific for every connection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |