continuous integration :: Pulse feature tour

Tool Support

build tools :: feature tour :: pulse continuous integration server

Pulse can run any build that can be run from a command-line, but also comes with support for popular build tools such as:

Pulse can also collect test information from popular testing libraries for direct integration in the build result:

Use another tool? No matter, you can add support using regular expressions or via a plugin!

SCM Integration

my changes :: feature tour :: pulse continuous integration server

Pulse supports CVS, git, Perforce and Subversion. Integration with these SCM servers allows you to:

Rich change information makes it easier to track down the cause of build failures.

Notifications

rss feeds :: feature tour :: pulse continuous integration server

Pulse supports notification of build results via:

Every developer has their own notification preferences which allows them to control how and when they are notified in a very flexible manner. This is critical to ensure developers get the notifications they need and none they don't.

Artifacts

artifacts :: feature tour :: pulse continuous integration server

Pulse terms all build output, including both output from commands and the files produced (binaries, packages, reports) as artifacts. You can easily configure your build to capture and store simple file or directory artifacts using Apache Ant style patterns. Artifacts can optionally be published to an internal repository and retrieved by dependent builds.

All captured artifacts may be browsed using AJAX-powered navigation in the Pulse web interface. You can even tie in HTML reports from other tools allowing them to be viewed from your build result in Pulse.

<< previous :: continue tour :: next >>