Pulse

Pulse project is an automated build (or continuous integration) server designed to work with you to ensure the integrity of your code.

Pulse regularly checks your source code out from your SCM, builds your projects, and notifies you of the results.

Features:

• Build any project: run arbitrary commands or use support for ant, make or maven.
• Capture build artifacts: files, directories, HTML reports. Filter collected files using wildcards.
• Extract information: find errors and warnings with regular expressions or built in support for ant, make and maven.
• SCM integration: for CVS, Perforce and Subversion. Trigger builds on change, view changes between builds, browse your repository.
• Build notifications: via email, Jabber IM, and RSS. Each user controls their own notification preferences.
• Flexible scheduling: trigger builds on SCM change, a Cron-like schedule, via the remote API or manually via the web interface.
• Build history: Browse and filter your project's build history, including working directories. Cleanup historical builds using flexible cleanup rules.
• Test reporting: test results are a first-class part of the build result. Test results read from JUnit-like reports.
• Flexible projects: choose simple configuration via the web interface or version your project configuration in your SCM.
• Build specifications: each project can have multiple specifications for different types of builds (e.g. continuous integration, nightly packages).
• Full web interface: setup, configure and monitor your pulse server. Build a project without editing a single text file.
• Build controls: view build queues and builds in progress. Set build timeouts or manually terminate a running build.
• User dashboard: users have their own, configurable view of the pulse server.
• Project homepage: a single page overview of recent project activity, including builds, changes and statistics.
• Local build: execute the pulse build engine in your own working copy of the project.
• Remote API: monitor, control and extend your pulse server remotely via XML-RPC

What is new in this release:

• This series has dozens of features and improvements, including browse view filtering, MSTest support, improved build and new agent comments, agent properties, upstream change reporting, downstream build notifications, simpler delivery of directories to downstream projects, property support in SCM configuration, a new warnings status, and much more.

What is new in version 2.3.11:

• A remote API method was added to access configuration state information.
• An important bug was fixed for users upgrading to 2.3 by skipping versions.
• Minor bugs were fixed.

What is new in version 2.3.6:

• This version series brings several major improvements.
• Concurrent builds of a single project are supported.
• Project and stage priorities were implemented.
• The project home and history tabs were renovated.
• The "my builds" and "build status" tabs were reworked.
• Plugins are automatically synchronized.
• The terminated build status was added.
• Google Test is supported.
• UI performance was improved.
• Much more was done.

What is new in version 2.2.7:

• The 2.2 series brings a number of new features and enhancements, with a focus on usability. In particular, the entire build reporting UI has been overhauled.

What is new in version 2.1.20:

• The ability to choose the revision for the build.
• Optional updating of your working copy to the build revision.
• Pluggable patch formats, with support for standard unified diffs.
• The ability to submit an existing patch file.
• A smarter internal patch format and with improved application.

What is new in version 2.0.40:

• Changes include: a new no-op SCM plugin, new configuration options to control agent pings, optional debug logging for git; and minor bugfixes.

What is new in version 2.0.39:

• Changes include a new property syntax allowing filters to be applied to property values, output logging for manually-triggered build hooks, and minor bugfixes.

What is new in version 2.1.7 Beta:

• Changes include the ability to run multiple agents in a single server process, improvements to consistency in transitive rebuilds, and minor bugfixes.

What is new in version 2.1.6 Beta:

• Pulse 2.1 includes several major new features and improvements. Some of the more important enhancements are detailed below.
• project dependencies:
• Pulse now boasts project dependency management, allowing you to declare dependencies between your projects and deliver built artifacts between them. Smarter triggering has also been added for dependent projects. Dependency support is built on Apache Ivy, making it interoperable with Maven and Ivy repositories, and with projects that already use Ivy. Pulse can act as an Ivy repository both for internal projects and external ones.
• multi-command projects:
• Pulse has always allowed a build to consist of multiple steps, but in previous versions to access this flexibility you had to write an XML file by hand. Now there is full UI support for configuring multi-command projects, and the full flexibility of all the commands has also been exposed in the UI. Of course, if you prefer, you can still write your XML files by hand (and even version them with your code).
• personal build improvements:
• Pulse personal builds allow you to submit your changes to Pulse for testing before you commit them. In 2.1, several improvements have been made to personal builds, including:
• * The ability to choose the revision for the build.
• * Optional updating of your working copy to the build revision.
• * Pluggable patch formats, with support for standard unified diffs.
• * The ability to submit an existing patch file.
• * A smarter internal patch format and with improved application.
• These improvements make requesting personal builds more flexible and interoperable. For example, you can create patches with other tools and submit them directly to Pulse.
• fine-grained cleanup rules:
• Cleanup rules allow you to reduce disk space usage by having Pulse automatically delete old and unwanted build data. In 2.1, there are more options controlling exactly what is cleaned up. This allows you greater control: for example you can remove old build artifacts but maintain the key build result information.
• built-in reference documentation:
• The documentation for Pulse XML files is now built-in to the Pulse server, so that it matches the exact version and plugin set you have installed. A link in the top right-hand corner of the UI opens this reference documentation.
• pluggable commands:
• As part of the changes for multi-command projects, both command configuration and the command APIs were overhauled. These changes make plugging in a command much easier than before. As with other configurable elements, commands can now be fully documented and integrated into the UI when plugged-in. Single command projects can use any plugged-in command with no extra effort for the plugin author.
• admin ui improvements:
• Multiple improvements have been made to the administration user interface. Most notable among these are:
• * A reduction in nesting in the configuration tree.
• * Performance improvements for large configuration sets.
• * A reduction in the number of files used to store configuration.
• These changes make the UI both simpler and snappier.
• much more...:
• Literally dozens more small features, enhancements, and fixes make 2.1 a compelling upgrade. Check the full release notes for more details!