Pulse Roadmap Update
Long time users of our Pulse Continuous Integration Server would know that we don’t believe in posting long-term roadmaps. They just never reflect a changing reality! But we have always been happy to discuss features with customers, including keeping our issue tracker (creaky old version of Jira that it is) completely open for all to see and contribute. In that spirit I’d like to talk a little about where we’re heading with Pulse in the near term, the bit that can be predicted, in a format more digestible than disparate issues.
The next version of Pulse (as yet unnamed), will have updates focused on a few areas:
- Upgrades of underlying libraries including Equinox, Spring, Spring Security, Hibernate, Jetty, Quartz, EhCache and more. If you haven’t seen a lot of visible changes reported recently this is why: these upgrades have occupied the first part of this development cycle. These are truly the most boring of all changes, which we hope you won’t notice directly at all! What you will notice, though, is a payoff of this strong foundation over time.
Major updates to the administration interface. The interface works well enough at the moment but could be improved in a couple of key areas: discoverability and efficiency. Key goals for these updates include:
- Improving the visibility of the most commonly-used configuration via overview pages.
- Making it easier to discover what is overridden (via templating) and where.
- More efficient navigation, especially through the template hierarchy.
- Modernisation to take advantage of HTML 5 (which the current interface predates).
These changes are big enough to warrant a dedicated blog post at a future point.
- Improved visibility of the build environment. When builds fail in curious ways the culprit is often a small difference in the environment. Pulse currently publishes environment information via implicit env.txt artifacts, but these haven’t kept up to date with the variety of options Pulse now gives for specifying build properties.
- Improvements to the Windows experience. In 2.7 work was done to improve Windows service support, but more could be done to streamline the setup process in particular.
As always we will also be working on dozens of smaller improvements and suggestions from our user base, most of which fall under one of:
- UI polish, especially in the reporting interface.
- Increased flexibility of project and build configuration.
- Updated support for modern versions of build tooling.
This entry was posted on Thursday, March 26th, 2015 at 2:30 pm and is filed under Agile, Build, Continuous Integration, Technology, Zutubi. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.