| | h2. Introduction |
| | |
| | Welcome to the {pn} 2.1 early access page! Here you will find new {pn} 2.1 milestone releases, along with information about what is new in version 2.1. |
| | |
| | | {note:title=EAP Complete}The {pn} 2.1 early access program is now complete. The 2.1 release series is now in *beta*, please see the [Zutubi website|http://zutubi.com] for more details.{note} |
| | |
| | h2. How To Participate |
| | |
| | Would you like to try milestone releases of {pn} 2.1? It's as simple as following these steps: |
| | |
| | 1. Download the latest milestone packages from below. |
| | 2. If you do not already have a license, you can download one from zutubi.com, or request one directly during the {pn} setup wizard. |
| | 3. Refer to the [Getting Started Guide] for information about how to install and start using {pn}. |
| | 4. Enjoy! |
| | |
| | h2. Reporting Bugs/Feature Requests |
| | |
| | During the early access program, we expect there to be some teething issues with the milestone builds. If you find such an issue, you can report it in our issue tracker. |
| | |
| | This is also a great opportunity to suggest minor features and enhancements that you would like to make it in to version 2.1. Such suggestions can be discussed on the forums or reported directly in our issue tracker. |
| | |
| | Our thanks to all who take the trouble to give feedback. You're helping make {pn} a better product for everyone! |
| | |
| | h2. Upgrading |
| | |
| | {note:title=Warning} |
| | If you are familiar with {pn}, you will know that {pn} runs through an automated upgrade each time you install a new version. At the moment, upgrading to 2.1, or even between 2.1 milestone builds, is *not* supported. |
| | {note} |
| | |
| | h2. Current Release |
| | |
| | The latest EAP build is 2.1.4, released on the 6th of August 2009. This release is an alpha build of 2.1, with major features having been started, but not yet completed. See from the release notes at the end of this page for more details. |
| | |
| | || Component||Version||Description ||Windows Installer||Tar Archive||Zip Archive||Instructions|| |
| | | Pulse | 2.1.4 | Alpha release | [pulse-2.1.4.exe|http://www.zutubi.com/download/pulse-2.1.4.exe] | [pulse-2.1.4.tar.gz|http://www.zutubi.com/download/pulse-2.1.4.tar.gz] | [pulse-2.1.4.zip|http://www.zutubi.com/download/pulse-2.1.4.zip] | Fasten your seatbelt! | |
| | |
| | h2. Known Issues |
| | |
| | The new features that have currently been added have complicated project configuration to some degree. We are actively working on ways to simplify the UI while keeping the full flexibility of the new features. |
| | |
| | {note}Pulse 2.1 is tested primarily in Internet Explorer 7 and FireFox 3. Some testing has been done in Internet Explorer 6, Firefox 2 and Safari, although some further issues are anticipated. It is not yet tested in other browsers.{note} |
| | |
| | h2. What's new |
| | |
| | Pulse 2.1 includes two major new features: |
| | |
| | h3. Build Dependency Support |
| | |
| | We have added support for delivering artifacts between project builds on top of an embedded [Apache Ivy|http://ant.apache.org/ivy/] repository. Projects can now publish artifacts to this repository, and declare dependencies on the artifacts published by other projects. These artifacts are delivered into the working directory of the build just after bootstrapping from the SCM. |
| | |
| | We are also adding support for smarter triggering between dependent projects. |
| | |
| | h3. Multi-Recipe Projects Without a Custom Pulse File |
| | |
| | Since version 1.0, {pn} has included a flexible core that allows you to define an arbitrary number of build recipes each with an arbitrary number of commands. In previous versions, however, the only way to use this full flexibility was to write an XML "pulse file" by hand. In 2.1 it is now possible to leverage the full flexibility of the core all via the web UI. On top of this we are also able to open up plugability of commands, which makes adding project types for new build tools easy. |
| | |
| | h3. Personal Build Improvements |
| | |
| | Several related improvements have been made to personal builds, giving developers more flexibility for testing outstanding changes. |
| | |
| | h4. Choose Build Revision |
| | |
| | You may now specify the revision to run a personal build against, rather than having it forced as the latest revision at the time of the build request. The personal build client walks you through available options (including current, floating and last-known-good revisions), or you can specify a custom revision of your choice. |
| | |
| | h4. No Forced Update |
| | |
| | In Pulse 2.0 and earlier, requesting a personal build forced an update of your working copy. Although we still recommend updating (to find conflicts early), you are now given the choice. Even if you do choose to update, you are not force to update to the latest revision (given you can also choose the revision as described above). |
| | |
| | h4. Pluggable Patch Formats |
| | |
| | Pulse now supports multiple formats for the patches submitted as part of a personal build. Apart from the existing format, plugins have been added to read standard patch files (unified diffs) and git patches (including git binary diffs). Pulse will even try to guess the patch format for you when it is not explicit. |
| | |
| | h4. Submit Existing Patches |
| | |
| | You can now submit patches from existing files, rather than based on the changes in a working copy. Along with pluggable patch formats, this opens up many new possibilities for submitting personal builds. With both the source and format of the patch being flexible, integration with other tools and workflows is possible. |
| | |
| | h4. Smarter Patch Creation and Application |
| | |
| | The support for pluggable formats also led to improvements to our existing format and the application of patches. The existing format now uses unified diffs where possible. On application, unclean patching is detected and reported. This is especially important when building against a custom revision. |
| | |
| | h2. What's missing |
| | |
| | We are still working on improving the {pn} 2.1 UI and hoping to get to a host of smaller features. These will appear in the coming weeks in further builds! |
| | |
| | h2. Release Notes |
| | |
| | Below are the changes between the EAP builds. |
| | |
| | h3. 2.1.4 |
| | |
| | {jiraissues:url=http://jira.zutubi.com/secure/IssueNavigator.jspa?view=rss&pid=10000&fixfor=10427&sorter/field=issuetype&sorter/order=DESC&tempMax=100&reset=true&os_username=confluence&os_password=confluence&decorator=none|columns=type;key;summary;status;resolution} |
| | |
| | h3. 2.1.3 |
| | |
| | {jiraissues:url=http://jira.zutubi.com/secure/IssueNavigator.jspa?view=rss&pid=10000&fixfor=10425&sorter/field=issuetype&sorter/order=DESC&tempMax=100&reset=true&os_username=confluence&os_password=confluence&decorator=none|columns=type;key;summary;status;resolution} |
| | |
| | h3. 2.1.2 |
| | |
| | {jiraissues:url=http://jira.zutubi.com/secure/IssueNavigator.jspa?view=rss&pid=10000&fixfor=10421&sorter/field=issuetype&sorter/order=DESC&tempMax=100&reset=true&os_username=confluence&os_password=confluence&decorator=none|columns=type;key;summary;status;resolution} |
| | |
| | h3. 2.1.1 |
| | |
| | {jiraissues:url=http://jira.zutubi.com/secure/IssueNavigator.jspa?view=rss&pid=10000&fixfor=10420&sorter/field=issuetype&sorter/order=DESC&tempMax=100&reset=true&os_username=confluence&os_password=confluence&decorator=none|columns=type;key;summary;status;resolution} |
| | |
| | h3. 2.1.0 |
| | |
| | {jiraissues:url=http://jira.zutubi.com/secure/IssueNavigator.jspa?view=rss&pid=10000&fixfor=10406&sorter/field=issuetype&sorter/order=DESC&tempMax=100&reset=true&os_username=confluence&os_password=confluence&decorator=none|columns=type;key;summary;status;resolution} |
