The pulse™ 2.5 beta program is now complete. Head on over to the Zutubi website for stable 2.5 builds!
Welcome to the pulse™ 2.5 beta page! Here you will find new pulse™ 2.5 beta releases, along with information about what is new in this version.
How To Participate
Would you like to try beta releases of pulse™ 2.5? It's as simple as following these steps:
1. Download the latest beta packages from below.
2. If you do not already have a license, you can download one from zutubi.com, or request one directly during the pulse™ setup wizard.
3. Refer to the Getting Started Guide for information about how to install and start using pulse™.
Existing Pulse Users
If you are currently using an earlier pulse™ stable version, we advise caution when trying out a beta release. These releases are not recommended for production installations.
If you would like to try a beta, we suggest using a staging server with a subset of your real configuration. This is a good way to discover any upgrade issues early, so they can be fixed for 2.5 stable releases which you can then use in production.
You may like to check out the Compatibility Notes to see if there are any changes that concern you.
Reporting Bugs/Feature Requests
During the program, we expect there to be some teething issues with the beta builds. If you find such an issue, you can report it in our issue tracker.
This is also a great opportunity to suggest minor changes and enhancements to the new functionality in version 2.5. Such suggestions can be discussed on the forums or reported directly in our issue tracker.
Our thanks to all who take the trouble to give feedback. You're helping make pulse™ a better product for everyone!
The latest build is 2.5.6, the first 2.5 release candidate build, released on the 11th of June 2012:
Pulse 2.5 is very much a user-focused release. We've always used feedback to improve Pulse, and this release is almost entirely feedback-driven. Key updates are outlined below.
filter main views
The browse and dashboard pages may now be filtered by build state. This allows you to easily find projects that are broken and need attention.
A new plugin has been added to process TRX reports produced by MSTest, integrating test results into your build.
separate warning status
Builds (and the steps within them) that include warnings now complete with a new warning status. This makes it easier to find, subscribe to, and generally work with builds with warnings.
The visibility of builds comments has been raised, making them easier to notice and access.
Comments may be left on agents, allowing communication between users. For example, an admin can make a note of why an agent has been disabled.
Properties can now be configured directly on agents, giving a simpler way to parameterise your build depending on the machine it runs on.
SCM configuration can now reference project properties. This allows you to parameterise your SCM settings, making them easier to maintain across many projects.
SCM support that is built upon command-line clients can now be customised using resources. This gives you simple control of the commands used for SCM integration.
As with agents, the Pulse master now supports a resource repository. Resources will allow you to customise tools used by the master outside of builds.
Build notification emails may now optionally have logs attached. This includes both the overall build log and output logs from each stage.
new stage hooks
Two new hook points have been added, allowing you to run a task just before a build stage is dispatched to an agent, or when a build stage is being terminated.
upstream change reporting
The build changes view now reports indirect changes via upstream dependencies. Similarly, the changelist view shows builds affected indirectly via downstream dependencies.
Committers may now be notified of build results that are affected by their changes indirectly via dependencies. This goes for both the email hook and personal subscriptions.
Directory artifacts can now be captured as a single archive file. When retrieved in dependent builds, you can opt to have archives unpacked automatically.
The build bootstrapping step has been made more flexible. You can now configure the path for clean builds, and can choose to skip the SCM boostrap if desired.
scm inclusion filters
SCM monitoring can now be customised with inclusive filters, complimenting the existing exclusion filters.
inverse resource requirements
Builds may now be configured to avoid agents that have a specific resource. This compliments the existing ability to assign builds by agent capabilities.
When a label is edited you are now prompted to choose whether all such labels should be renamed. This makes renaming existing labels much simpler.
The ability to clean up build directories has been classified as a separate permission, allowing finer control of user access.
subversion 1.7 support
The Subversion plugin now has support for Subversion 1.7 format working copies. This allows personal builds to be submitted easily from the new working copy format.
perforce stream support
The Perforce plugin has been enhanced to support streams, a kind of built-in branching model in newer Perforce releases.
git submodule support
The git plugin has been enhanced to support submodules, allowing Pulse to automatically update selected (or all) submodules when bootstrapping builds.
This release also includes numerous smaller improvements and fixes. These include UI refinements, remote API additions, better artifact retrieval feedback, better Subversion externals support and much more.