Projects tagged ‘mercurial’ and ‘subversion’

The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has ... [More] changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve. [Less]

Tailor is a tool to migrate changesets between ArX, Bazaar, Bazaar-NG, CVS, Codeville, Darcs, Git, Mercurial, Monotone, Perforce, Subversion and Tla repositories.

cvs2svn is a Python script that converts a CVS repository to a Subversion repository. It is designed for one-time conversions, not for repeated synchronizations between CVS and Subversion.

The Ohloh Source Control Management library is an abstraction layer for source control management systems, allowing an application to interoperate with various SCMs using a single interface. It was ... [More] originally developed at Ohloh, and is used to generate the reports at www.ohloh.net. [Less]

Transifex is a system that facilitates the process of submitting translations in various version control systems (VCS) by acting as a proxy for these submissions for a whole translation community. The ... [More] name literally means "translation-builder" (from the latin verb facere). [Less]

Project Builder (aka pb) helps you package your software from your CMS (Subversion or CVS currently) to multiple distributions (mandriva, fedora, openSuSE, debian, ubuntu, gentoo to name a few) either ... [More] locally or using virtual machines (qemu currently). It's written in perl and is derived from the build system made originally for the MondoRescue project, completely rewritten to be project independant and support others such as LinuxCOE or collectl. [Less]

Yet another VCS browser (like ViewVC) and a kind of analyzer providing multiple statistics about repository content and developer activities. Targeted to work with Subversion, GIT and Mercurial. ... [More] Currently at the planning and 'proof of concept' phase. Here comes the requirement page. [Less]

You can use hg for diary work, and svn for all the crew, without the crew have knowledge about hg. Also the motivation for this project is by able to do something like: - (hg ci)+ - hg up ... [More] last-svn-synch - svn up + hg ci -Am "rev 123" -> new head - hg merge + hg ci - svn ci With the nice to have uncollapsed optional change history from svn, and from hg to svn [Less]

IntroductionWhen trying to develop small to medium size projects, you often skip setting up big and complicated CI (Continuous Integration) tools such as Buildbot. Who would want to set up an almost ... [More] enterprise tool, that could drive away hours of development when all you need is something simple to continuously check for errors every time you commit code to a repository? Main objectiveTo run CUSCO once in one terminal while you work on your IDE or on another terminal. You commit your code and you see your tests in real time. Dependencies and VersionsBefore running everything please NOTE that CUSCO was developed with Python 2.6 You will also need: Pylint Nose CUSCO will not run unless these dependencies are met. OptionsFor full options run: python cusco.py --helpYou will always need to supply a path. To start serving right away: python cusco.py -p /path/to/directoryCurrent Limitationscusco will only run with HG (Mercurial) and has limited options. For now, it will only run the tests against an existing path with code and will return the results via Nose at the terminal. Feature ListHave a Master Cusco Daemon that runs somewhere else and you can connect remotely. Configuration files for different scenarios. You always need the options! SVN support. Email alerts Multi-threaded tests for several instances/scenarios [Less]

A way to integrate VCS-agnostic repository browsing into Django apps. Initially, Subversion and Git will be supported (and hopefully Mercurial as well), but if anyone is interested in supplying other functionality, please let us know.