AnthillPro is a build management and lifecycle automation server for the enterprise that makes the build and release process easy and efficient. As a continuous integration server, it can produce a new build for every developer check-in. The entire team can be alerted to problems via email or instant message. Each build can then be promoted to higher statuses, or deployed to various servers and environments using your scripts. At every step, AnthillPro records who did what to keep your auditors happy.
The Helix Ribosome build system is a set of programs written in the Python programming language which provide a common interface to retrieving and building programs from source code stored in a CVS repository. The build system is made up of two basic subsystems. The first ("build") calculates the dependencies of a target, retrieves the source code, and runs commands to build that source code in the correct order. The second component ("Umake") is a cross-platform Makefile generator, which generates makefiles that work with MSVC, CodeWarrior, and typical Unix toolchains. Umake can be used independently from the build program.
Cameleon is an integrated development environment for Objective Caml and eventually other languages. Its features include a graphical user interface, configuration management based on CVS, easy access to and browsing of documentation, various editors, customizable file types, a plug-in architecture, and a highly customizable interface.
F-Watch is a kernel module that reports changes on files to /dev/fwatch. It hooks into the sys_calls and does not require a kernel patch. To activate watching for certain events, users need to run ioctl to register the wanted events; examples are in the src dir. Ioctl can be used during runtime to individually change the required events.
The CVS Accesslist Patch is a safe way to keep users accessing only the modules you specify. It works simply: A person is only able to perform CVS operations if he has a copy of the original module on his machine. It has a configuration file under the CVSROOT tree; in this file, you specify which user will be able to access the modules in your repository.
The Distributed Concurrent Versioning System (DCVS) extends the well-known version control system CVS and the file distribution and synchronization program CVSup with functionality to distribute CVS repositories with local lines of development and handle synchronization of the distributed repositories automatically in the background. Development lines (branches) are owned by a repository server, repository servers efficiently update each other via CVSup, and CVS ensures correct server use on checkin and branch creation.
CVSreport produces text or enhanced HTML activity reports from a local or remote CVS repository. It can be used to extract activity information from any timespan, or to automatically generate reports and store/send them on commit events. It can extract changesets (a set of commit operations which happen along a single invocation of the cvs commit command) from a CVS repository history. Used from the client side, it produces a report starting from an arbitrary date from a simple working copy. On the server side, it can automatically generate reports and mail them upon commit.
Cvs-Brancher establishes a tagged branch in a CVS module and schedules a merge and build to occur at a later date/time. It might be used to roll out Website changes at odd hours, such as posting a press release in time for the start of the business day on the east coast, or to roll out cfengine changes to a data center during the night, to minimize the impact of downtime.