adaptability :: Pulse feature tour
Unlike some continuous integration servers, Pulse does not force you to adapt your project to suit the build system. Recognising that all projects are different, we designed Pulse to be as adaptable as possible so that it can work the way that you work, out of the box.
Layers of flexibility
Flexibility is a great thing, but it often comes with complexity. This is avoided in Pulse by a careful layered design. Simple things are kept simple with a comprehensive web interface. However, it is possible to drop down to a more powerful layer when necessary. This layering appears in several parts of Pulse, wherever it integrates with your environment.
Customisation
Pulse provides rich integration, even with unusual build environments, by allowing customisation. A Pulse build can run an arbitrary sequence of commands, and you can capture output artifacts (files, packages etc.) using powerful patterns. Then you can extract useful information from your build artifacts using regular expressions. The mechanisms are simple, but their combination is powerful.
Integration into your environment
Pulse doesn't just adapt to your build system. It can adapt to your whole development environment by integration with various tools, including:
- LDAP servers: authenticate users via LDAP, and integrate your LDAP groups.
- SCM server browsers: link SCM change information from Pulse to an external change viewer (such as Fisheye).
- Bug trackers: link from key phrases in your commit messages to bug reports in an external tracker.
- And more: Pulse provides both a remote API (XML-RPC) and various hooks to allow more in depth integration.
