Continua CI 1.7 Version History

• Update: Can now specify multiple files for JUnit Import action using ANT patterns.
• Fix: Various issues with display of unit test results for JUnit Import action .
• Fix: Javascript error when logged in as guest preventing display of dashboard content.
• Fix: Issue with Tag Repository Changeset build event handler where wrong changeset would be tagged when more than one changeset was associated with the build.
• Fix: Issue with Tag Repository Changeset build event handler only listing repositories set to detect tags.
• Extra debug logging and error handling.
• Minor display fixes and text updates.

Note : You will need to update your agents after installing this build

• Update: Now showing unread private messages in bold.
• Update: Long file path support was not implemented for artifacts.
• Fix: Issue where concurrent stage limit was ignored when matching exactly one available agent.
• Fix: Error when curly brackets were entering into variable description.
• Minor updates to text, error handling and help links.

Note : You will need to update your agents after installing this build

• Update: Added context field to GitHub status build event handler
• Update: Now showing agent name in running builds lists
• Update: Better detection of case renames in Git repositories
• Update: Updated bundled Mercurial to version 3.5
• Fix: Could not add or remove variable expressions on trigger dialog
• Merged in fixes from v1.6.0.311.

Note : You will need to update your agents after installing this build

• Merged in fixes from v1.6.0.305.
• Update: Now validating the syntax of regular expressions entered into repository and trigger fields.
• Minor display changes.

Note : You will need to update your agents after installing this build

• Fix: Subversion: Fixed regression bug causing an error when creating tags.
• Fix: Started field was not updating on Builds View.

New Version 1.7 Features

• New Builds View dashboard This view is useful for project administrators and shows a list of active builds across all viewable configurations. This includes running builds, queued builds and builds awaiting promotion.

New panel of indicators

• Some important numbers including the total count of queued and running builds, as well as available agents and concurrent build licenses.

New Repositories tab

• This is accessed via the Configurations view and shows status of each repository.
• We've also included “Check Now” buttons for immediately polling each repository. You can also initiate repository checking from all existing repository pages

Project-wide and configuration versioning options.

• Project-wide versioning: The build version number can now be incremented across many configurations within a project.
• Build number re-use: A new option at the project or configuration level to decrement the version counter when a build is discarded while initialising. e.g. due to configuration conditions. Please note that the build number will be decremented only if no other build has started in the mean time and is using a later build number

Improvements to Build Completed triggers.

• Variable expressions: You can now use expressions when defining variables allowing you to passing information from triggering to triggered build.
• New conditions tab: This allows to use expressions to control whether a build is triggered.

Improvements to Repository triggers.

• Trigger on specific file change types: Triggers can now be set to start only when the changeset contains certain types of file changes e.g. additions, modifications and deletions.
• Trigger file pattern: You can now specify a file pattern for repository triggers to restrict triggering only to changesets containing matching files.
• Trigger comment pattern: You can also limit triggering to changesets with specific text in the comment.

New node.js actions.

• Package management with Npm and Bower.
• Grunt and Gulp build runners.
• Unit testing with Mocha.

Additional Improvements

• New force repository check option in queue build dialog allowing control over whether to recheck repository when building. There is also a default setting for each configuration.
• Improvements to Stop Build buttons on dashboard view to ensure that the build stopped is always the latest build at the time when the button was clicked. Stop build dialogs also now display the build number of the build being stopped.
• New build event handler for posting status updates to a Stash server
• New comments field on all actions – displayed as a tooltip in Stages editor.
• New ContinuaCI.* system environment variables are now available to all executable actions.
• Execute Program, DOS Command and PowerShell actions now include an option to generate a context XML file. This file contains details of the build including repositories, changesets and files for you to parse with you own script or program
• Case-only renames are now recorded in the repository cache for Git repositories.
• New option to list author instead of committer as changeset username for Git repositories.

Note : You will need to update your agents after upgrading the server to this build.

Previous versions