Pulse is a continuous integration server (or build server) designed to be easy to use while offering powerful features. It regularly checks your source code out from your SCM, builds your projects, and notifies you of the results. Key features include simple setup and administration using an AJAX-powered Web UI, adaptability to existing environments, distributed building, personal builds (test using Pulse before committing), and individual developer dashboards and notification preferences.
Anthill is a tool that ensures a controlled build process and promotes the sharing of knowledge within an organization. Anthill performs a checkout from the source repository of the latest version of a project before every build and tags the repository with a unique build number after every build. It supports many reposistory adapters including: CVS (Concurrent Versions System), Visual Source Safe, Perforce, PVCS, StarTeam, MKSIntegrity, and FileSystem. Anthill also automatically updates a project intranet site with artifacts from the latest build. Anthill is an extension to the Apache-Ant project and is compatible with version 1.3, 1.4, and 1.5 of Ant.
Parabuild is a software build and release management system. It helps software teams and organizations reduce risks of project failures by providing practically unbreakable scheduled, release builds and Continuous Integration. It supports Perforce, Subversion, CVS, Surround SCM, AccuRev, ClearCase, Serena ChangeMan (PVCS), Borland StarTeam, SourceGear Vault, Visual SourceSafe, and MKS Source Integrity.
Clover makes the gathering and analysis of code coverage metrics as painless as possible. It features include tight integration with the Jakarta Ant build tool and accurate, configurable coverage recording. It gathers Method, Statement, and Branch coverage data. Compile-time properties and source level directives allow for precise control over the coverage gathering process. Coverage data can be viewed in XML, HTML, or via a Swing GUI. Report-time options allow for the exclusion of particular statement types from coverage analysis. Plugins for the Eclipse, NetBeans, JDeveloper, JBuilder, and IntelliJ IDEs are provided.
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.
CUT is a unit-testing framework for C, C++, and Objective-C. Unlike other unit testing tools, CUT doesn't strive to be an SUnit clone. It automates a lot of the drudge work often encountered when using other unit testing packages for the C family of programming languages. CUT may also be used to unit-test assembly language software in some circumstances.
JCSC is a powerful tool that checks source code against a highly definable coding standard for potentially bad code. Standards cover naming conventions for classes, interfaces, fields, and parameters, and the structural layout of classes and interfaces. Each rule is highly customizable. It can also find potential bugs, including empty catch/finally blocks, switches without defaults, throwing 'Exception' types, and slow code. JCSC was inspired by lint.
Autobuild is a package that processes output from building software, primarily focused on packages using Autoconf and Automake, and generates HTML summaries. The output includes project name, version, build host types, build host name, and indication of success or failure. The output is indexed in many ways to simplify browsing.
Jamit (Java Access Modifiers Inference Tool) allows you to infer tighter access modifiers for Java code. Analyzing bytecode, it can find out if fields or methods may be declared private, default, protected, or final. Engineering software with Jamit can thus help increase hiding and keep interfaces as small as possible. The most useful application for Jamit is dead code elimination. Jamit can be used to find out which methods and classes are unreachable and automatically eliminate the corresponding code, saving space for binary distributions.