new in Pulse 2.6
The latest release of Pulse, version 2.6, is now available! Pulse 2.6 contains a raft of new features and improvements in a broad range of areas. A summary of notable changes can be found below.
concurrent personal builds
Admins may now allow users to run multiple personal builds in parallel. For developers on large projects, this can significantly reduce the time to feedback for changes they are working on. It also allows better utilisation of build agent resources.
As always with personal builds, empowering developers to test their changes before committing them means less chance of disruptive regressions on the mainline.
run hooks on agents
Pulse has long allowed you to run tasks at hook points in builds. Until now hooks have always run on the master, limiting their use in some situations. In Pulse 2.6, you may now choose to run hooks on agents, opening up new possibilities.
For example, you could hook in custom cleanup actions when a build needs to be terminated.
dynamic report fields
The ability to capture and chart metrics during a build has been made more flexible. When defining your own reports, you can now reference fields dynamically using wildcards. So if your build starts producing a new metric, it is automatically added to charts.
Capturing and charting custom metrics is a great way to implement performance "drift" tests. In Pulse dynamic fields makes this even simpler.
Pulse has always supported automatic cleanup of your old builds using cleanup rules. New in 2.6, we've added the inverse: build retain rules. These make it much simpler to ensure a certain subset of your builds are never cleaned up.
Retain rules are designed to complement the existing ability to "pin" important builds.
configuration export and import
The Pulse master now includes commands to export and import a subset of your configuration. The exported configuration can later be imported into a compatible Pulse version.
This mechanism can be used to transfer configuration between servers, or to archive old configuration that you would prefer to remove from your live instance (but aren't ready to fully discard).
A new "manual" trigger type is now supported in your project configuration. The default manual trigger for projects is configured in this way, so you can customise it and/or add additional manual triggers. You could even remove the default if you don't want a project to be triggered manually.
Given that triggers can define properties used in the build, the ability to add manual triggers is a powerful way to set up multiple build configurations.
Cron triggers, the most flexible way to run builds on a time-based schedule, may now be configured to automatically pause after firing. This allows them to be used as one-shot triggers: where you want to set up a single build to run at a particular point the future.
One-shot triggers are great for setting up a specific build to run in a quiet time, such as the weekend.
cancel all builds
It is now simple for Pulse administrators to cancel all queued and/or active builds. New actions have been added to the server activity view specifically for this purpose.
This simple addition can be used in conjunction with pausing queues to enforce a quiet time for maintenance.
- concurrent scm polls: now supported for a single SCM server.
- expanded remote api: access to server history, agent state and upstream changes.
- improved test case handling: flexible duplicate handling and smarter trimming of long messages.
- dashboard optimisations: making this view snappier in large installs.
- git shallow clone support: save time and disk space for large repositories.
- smarter clean build detection: eliminates unnecessary rebuilds on small configuration tweaks.
- trigger hook permission: distinct from project write permission.
Dozens more small features, enhancements, and fixes make 2.6 a compelling upgrade. Check the full release notes for more details!
try it out
You can download and try Pulse 2.6 free today. Be sure to let us know how you go: we love feedback!