a little madness

A man needs a little madness, or else he never dares cut the rope and be free -Nikos Kazantzakis

Zutubi

Pulse Continuous Integration Server 2.2!

Big news today: Pulse 2.2 has graduated to stable! This release includes a stack of new features and improvements, including:

  • Build UI overhaul: all tabs improved and restyled.
  • New logs tab: making it easier to access stage logs.
  • Featured artifacts: choose which artifacts should appear prominently.
  • Build navigator: easily move forward and backward through history.
  • Working copy browser: view working copies for in progress builds.
  • Move refactoring: move projects and agents in the template hierarchy.
  • Template navigation: navigate directly up and down a hierarchy.
  • Subscription by label: subscribe to notifications by project groups.
  • Agent executing stages: see what all agents are building at a glance.
  • Subversion exports: for faster and smaller builds.
  • Performance improvements: key for larger installations.

See the new in 2.2 page for full details.

In conjunction with this release, we’ve also given our website a complete overhaul. The new site has a fresher look, and communicates the key features of Pulse more directly. The updates also include some new features:

  • RSS feeds for news items.
  • Links to our latest blog posts on the front page.
  • An improved buying process, allowing multiple licenses to be purchased in one transaction.
  • Self-service renewal payments – just enter your current license key and go!
  • A more user-friendly downloads page.

We hope you enjoy the new release, and the new site. And please, let us know what you think!

Liked this post? Share it!

3 Responses to “Pulse Continuous Integration Server 2.2!”

  1. October 11th, 2010 at 8:50 am

    Mateusz Loskot says:

    Hi,

    I admit the Pulse server looks very interesting.
    I’d have two questions which perhaps could be answered:

    1) Are you going to support CMake?

    2) Could you post some comparison of Pulse versus Buildbot and Hudson?

  2. October 11th, 2010 at 11:35 am

    Jason says:

    Hi Mateusz,

    I’m glad to hear that you are interested in Pulse! In response to your questions:

    1) We don’t have direct support for CMake, although I believe it creates regular makefiles so you can leverage our support for that. You can certainly run CMake (and in fact any command) from Pulse — Pulse projects are built using recipes which can include multiple commands. You can use a Pulse executable command to run CMake, then a make command to run the build itself. We could also add a specific cmake plugin, which would make this configuration more convenient (but would work in much the same way).

    2) We don’t like to delve too deeply into comparisons, as it is hard for us to be fair to the other tools (which obviously we don’t know as well as Pulse). What I can say is what we think the strengths of Pulse are, including:

    – The web interface, which is comprehensive (both for reporting and configuration). In Pulse everything can be configured in the web UI, and all users get their own dashboard and preferences etc.
    – Our unique templated configuration system, which allows you to keep your configuration DRY. We learned early on that when managing even a few projects (and different builds for the same project), that a huge amount of the configuration overlaps. So we have created a powerful templating system, integrated into the web UI, which allows you to easily share common configuration between projects.
    – Easy distributed building by installing Pulse agents on multiple boxes. Again all managed via the web UI. You can have builds assigned to agents based on their capabilities (e.g. what OS they are running, what compilers are available etc).
    – Personal builds, which allow you to test your changes before you commit them to your SCM. This beats the traditional model of checking in first and running the risk of team members picking up your change before it is known to build successfully. Using personal builds you submit your patch directly to Pulse first and can see on your dashboard how it builds before you choose to commit it.
    – Simple administration, which saves a lot of time. Pulse does as much of the mundane admin work for you as possible. For example, upgrades are simple: you install a new version and it automatically upgrades your existing data and then upgrades your agents for you.

    I hope that gives you some idea. If you have any questions, feel free to email me at [email protected].

  3. October 13th, 2010 at 1:10 am

    Mateusz Loskot says:

    Jason,

    Thank you very much for this very comprehensive response.
    I will try to describe my goal and e-mail you directly.

    Mat

Leave a Reply