Continua CI 1.9.1 Version History


March 30th, 2020


  • Fix: Issue where Python VirtualEnv action would fail when more then one build was running concurrently.
  • Fix: Renamed files where not listed in changesets for Git repositories due to a change in 'git log' output.
  • Fix: Recently added Log Script Output option was not set to true on existing PowerShell actions.

  • Update: Added property collector for Run DOS Command / Batch File action for agents where COMSPEC environment variable was missing.

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


March 24th, 2020


  • Fix: Issue where build could start before a forced repository check was completely finished.
  • Fix: Minor issue where edited item was not refreshed on Issue Connectors page.
  • Update: Added Test Adapter Path and Parallel options to VS Test action, plus additional text field to enter a custom Framework version.
  • Update: Removed warnings about LogOutput or CheckExitCode option when WaitForCompletion was not enabled for Execute Program, Run DOS Command / Batch File and PowerShell actions.
  • Update: Additional DotNet Core versions available to DotNet property collectors and actions including runtime version 5.0.0-preview.1.20120.5 and SDK versions 3.1.200 and 5.0.100-preview.1.20155.7.
  • Update: The expression $Source$ now returns the path of the repository if there is one, and only one, repository.

  • Some third party package updates.

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


March 13th, 2020


  • Fix: Regression bug in v1.9.1.614. An error occurred while saving (and loading old) report definitions.
  • Fix: Issue where sensitive variables in action arguments were not masked in build log.
  • Fix: Issue where agent installer would not update configuration file when upgrading and specifying new settings.

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


March 10th, 2020


  • Fix: Regression bug in v1.9.1.614. An error occurred while saving new repositories, due to a default datetime value which was incompatible with changes we made to ensure that a correct UTC datetime was stored to database.

  • Update: Updated permissions on repository Mappings button to provide access to mappings for all selected branch-aware repositories, regardless of scope, to anyone with Configuration.Editor permissions.
  • Update: Changes to default error message patterns to include Visual Studio action, and to default warning message patterns to include Visual Studio and DotNet actions.

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


March 4th, 2020


  • Fix: Corrected datetime expressions, e.g. $Build.Started$, to output local server time instead of UTC time. Note: this could be a breaking change if you are passing a datetime value to another service that expects a UTC datetime. Resolve using the UTC function e.g. $Build.Started.UTC()$.
  • Fix: Local and UTC functions in datetime expressions now work correctly.
  • Fix: Corrected datetime variables in notification templates to output local server time instead of UTC time.
  • Fix: Reverted update to DotLiquid templating engine which caused errors when using 'truncate' filter in templates.
  • Fix: An error was occurring when using a branch with a length of more than 256 characters.

  • Update: Changed 'delete build' icon and moved it to left of other buttons.
  • Update: Update to DotNet Core versions available to DotNet property collectors and actions to include runtime versions 3.0.3 and 3.1.2 and SDK versions 3.0.103 and 3.1.102.

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


March 2nd, 2020


  • Feature: Builds can now be deleted from the build history via a new 'Delete Build' button added to the Build View toolbar. Users must have the new Builds.Delete permissions before they can delete builds.

  • Update: Branch lists on the Configuration Repository Branch Mappings dialog can now be sorted by descending last commit date by setting the server property 'Server.BranchMappingsDialog.SortBranchesByDescendingLastCommitDate' to 'True'.
  • Update: The scheme and port of repository URLs can now be changed for each repository without recreating the repository and changing its ID.

  • Fix: The Directory Path Variable for the For Each Directory action is now populated with the full correct path on each iteration.
  • Fix: Issue where File System repository pointing to a UNC path would record a changeset when no files had changed.
  • Fix: Database time-out when getting the latest branch tag for a repository with a large number of changesets.
  • Fix: Removed incorrect error messages logged when notification published are paused due to rate-limiting.
  • Fix: Queue build buttons on the Changes view table are no longer displayed if the logged-in user does not have permission to start builds.

  • Some third party package updates.

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


February 20th, 2020


  • Feature: Builds can now be queued for a specific revision or commit id, either from the Queue Options dialog or the Changes view for the configuration.
  • Feature: Trigger quiet periods can now be set up to end at a specific time of day, in addition to the current time interval.

  • Update: A Build Tags column has been added to the Builds dashboard view.
  • Update: New file system repository changesets will now be commented with the date and time of change detection.
  • Update: Added .fbx8 to list of valid project file extensions in FinalBuilder action.
  • Update: Search box on Publishers page in Administration section now searches for publisher names containing text rather than starting with text.

  • Fix: A empty string entered as left or right value of expressions used in conditions is no longer treated as a null.
  • Fix: Issue where server thinks that builds are still running after agent restart.

  • Minor UI fixes.
  • Various third party package updates.

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


February 5th, 2020


  • Feature: Added a new "use internal logger" option to the DotNet Test action. This automatically logs and imports test results into the database for display on the Unit Tests tab of the Build view.
  • Feature: Added an option to repository triggers to trigger on the default mapped repository branch for the configuration.
  • Feature: A tag change icon is now displayed next to any changesets which represent a tag change.
  • Feature: Added new property collectors for the latest .Net Core versions.

  • Fix: Removed unsupported .Net Core target frameworks from XUnit action.
  • Fix: Git repositories had stopped detecting tag deletions and updates.
  • Fix: Repository and Build Completed trigger descriptions are now updated when the name of the associated repository or configuration is changed.
  • Fix: Handled possible null exceptions in XUnit test result parser.

  • Update: Git repositories now fetch any updates to submodule tags before writing to the changeset details xml file.
  • Update: Added protection lock and warning to Name field when editing repositories and variables as expressions references these names are currently not automatically renamed.
  • Update: Improvements to handling of decryption errors - allowing stage actions to be edited if decryption keys have changed.
  • Update: Improved handling of errors associating changesets.

  • Some third party package updates.

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


January 6th, 2020


  • Regression bug in v1.9.1.538: Error when creating a new build configuration.
  • Update: Any changeset details XML files saved when checking out repositories are now automatically registered as artifacts.

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


December 20th, 2019


  • Fix: Regression bug in v1.9.1.538. The version counter was missing serialisation attributes and was displayed as zero when editing configuration details.


December 19th, 2019


  • Feature: Added new Mattermost notification publisher.
  • Feature: New server properties "Server.QueueOptionsDialog.SortBranchesByDescendingLastCommitDate" and "Server.QueueOptionsDialog.SortTagsByDescendingModifiedDate". Set the former to "True" to sort the Branches drop-down list in Queue Options dialog by descending last commit date, and set the latter to "True" to sort the Tags drop-down list by descending modified date.

  • Fix: The "accumulate changesets" setting of configuration conditions is no longer lost when saving changes to configuration Details tab and is now pre-populated with the current value when creating a new condition.
  • Fix: Added batching and retries when adding changeset files to the database to handle time-out errors.

  • Update: Performance improvement when detecting case-renamed for changesets with a large number of file changes.
  • Update: Improvements to bubble text display on configuration Metrics charts.
  • Update: Small improvements to display of optional fields in default notification templates.


December 10th, 2019


  • Fix: Stage links in build event handlers were being lost when cloning a configuration. They would then subsequently be disabled when further configuration changes were saved.
  • Fix: Private messages had stopped working.
  • Fix: Links to build and stages were broken on Builds View of project dashboard.
  • Fix: Expression escaping in request body of HTTP Request build event handler now works for expressions ending in a function call.
  • Fix: Default "Configuration Updated' notification templates did not display configuration name correctly.

  • Update: Improved handling of repository case-collisions, i.e. when a file or folder exists with same name but different case in different repository branches.
  • Update: The range of the Build Time and Queue Times charts on the Detailed View of project dashboard now start from zero instead of number based on the minimum value.
  • Update: Build metrics are now populated in expressions used in build event handlers. e.g. $Build.Metrics.UnitTests.Passed$.
  • Update: Any carriage returns '\r' in the request body of the HTTP Request build event handler are now removed and replaced with newlines '\n'.
  • Update: Any escaped control characters, e.g. '\n', '\r' and '\t', in function parameters are now output un-escaped (as newlines, carriage returns and tabs). e.g. $Utils.GetString("a\nb\nc").Replace("\n", " ")$ => "a b c".
  • Update: Added a new ReplaceNewlines function to string expressions.
  • Some third party package updates.

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


November 29th, 2019


  • Feature: Added a list of the latest 10 completed builds to the Builds View.

  • Update: Various updates/fixes for build comment, pin comment and build tag editing:
    • improved maximum length validation.
    • corrected display of long tag names and long comment lines.
    • white space within build and pin comments is now preserved when editing and displaying.
    • another user's build comments can now be edited by configuration administrators.
    • last edited user and date/time is displayed when build comments are edited.
  • Update: The list of Latest Warnings is now logged when an action succeeds (as well as when it fails).
  • Update: Messages marked in the FinalBuilder log as "Error Ignored" are no longer listed in the Latest Errors shown in the build log when the action fails, or in the $Build.ErrorAndWarningLogMessages$ expression or notification variable. Requires FinalBuilder v8.0.0.2694.
  • Update: Added $Build.Created$ and $Build.Started$ expressions.
  • Update: Improved error handling for actions which update server values. i.e. Set Build Version, Pin Build, Tag Build...

  • Fix: Error when using FinalBuilder action with Using field set to Custom.

  • Some minor UI updates.

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


November 18th, 2019


  • Fix: Regression with Stop action where stopping a stage would also stop build.
  • Fix: Assemblies needed for File Transfer action were missing from server installation.
  • Fix: Casting error when validating File Transfer action.

  • Update: File Transfer action now supports TLS 1.3 with the FTPS transport protocol.
  • Update: Increase to the size of the user property value field in the database, to allow a larger number of hidden configurations.
  • Update: Promotion dialog now shows the name of the stage that is being promoted to.

  • Some third party package updates - including fix to PostgreSQL driver issue where idle connections were not closed.

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


November 15th, 2019


  • Fix: Issue converting decimal values when reading unit test metrics from new SQLite build log database when the current regional number format uses a comma rather than a dot for the decimal separator.
  • Fix: FinalBuilder action -htmlstyle command option was applied when using older versions of FinalBuilder which didn't support it.
  • Fix: ToText() function on ErrorAndWarningLogMessages and TailLogMessages expression properties was throwing an exception.

  • Update: Now returning zero instead of an error when no value has been recorded for a metric such as $Stage.Metrics.UnitTests.Failed$. i.e. when stage is empty.
  • Update: Now returning an empty string instead of an error when index is out of range for string collection expression Items. e.g. $Utils.GetString("a,b,c").Split(",").Item(9)$.
  • Update: Improvements to display of tiles on Repositories tab of Build view.

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


November 13th, 2019


  • Feature: Added a new Variables tab to the Build view, showing a list of all variables which can be updated during the build and their values at the end of the build.
  • Feature: Added Reset buttons to each configuration on the Manage (previously Finished) tab of the Project Wizard. This allows removal of all configuration builds, without changing the cleanup policy, and zeroing of build version counter
  • Feature: Added support for a new 'addBuildComment' custom log message. This allows programs running under Continua CI to add a build comment by writing a message to standard output. E.g. Console.WriteLine("@@continua[addBuildComment comment='This build was deployed to production' replaceExisting='true']");

  • Update: The build log now uses SQLite as the database engine instead of SQL Server Compact Edition which has been deprecated. This should improve log insert performance during build and responsiveness when reading build log. Note there will be a few seconds delay the first time you view an existing build log while the data is migrated to the new database format.

  • Update: The character limit when editing build comments has been increased from 1024 to 10240 characters.
  • Update: The confusing validation message from FinalBuilder action when the Log Export File has not been specified has been removed.
  • Update: The metadata view shown when hovering over filenames on the build Artifacts page no longer appears for files without any metadata and now includes correct metadata for image files.
  • Update: The Finished tab of the Project Wizard has been renamed to Manage.

  • Fix: Issue where Stop action did not stop the build (only the stage) when set to stop 'Stage And Build As Failure'. The 'Stage And Build As Failure' Stop setting option has also now been replaced with separate 'Stage As Failure' and 'Build As Failure' options.
  • Fix: Issue where tabs on the Build View and Configuration View pages did not refresh correctly when the browser back and forward buttons were used
  • Fix: Issue where the successful builds associated with changesets on the Changes tab of the configuration were no longer displayed after a repository was reset
  • Fix: Issue where newlines were only replaced in CommentHTML build notification variable if there was an associated issue connector
  • Fix: Corrected remaining count when editing build comments.

  • Some minor UI changes
  • Some third party package updates

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


October 28th, 2019


  • Update: The DotNet Core property collectors updated to include later versions of the .Net Core runtime and SDK.
  • Update: The queued and running build count indicators in header now show the total number of builds for all users (rather than counting only those viewable by the current user).
  • Update: Improvements to performance when querying changeset and repository details from the database. You should see the Repositories tab on the configuration tab load faster if you have a lot of changesets in the database.
  • Update: Newlines are now preserved as as HTML breaks in the CommentHtml property of changeset objects in notifications and expressions.
  • Update: Improvement to sort order of NetCore.App and SDK Version selection options for DotNet actions.

  • Fix: Issue with missing images on build metrics charts.
  • Fix: Error when Custom value is used for the Using field for FinalBuilder actions.
  • Fix: Installer updated to handle missing XML attributes when updating configuration files.

  • Some third party package updates.

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


October 15th, 2019


  • Possible breaking change: Removed all support for SQL Server 2005 databases and upgraded any existing SQL Server 2005 settings to SQL Server 2008. Note that SQL Server 2005 has been out of Microsoft support since April 2016.
  • Possible breaking change: The StageCompleted build state is now in the Running state category. This means that a build at this status will be included in the $Configuration.RunningBuildsCount$ expression and, once the initialisation stage is over, each build will stay in a queued or running state until the build is finished.

  • Fix: Migrated any existing datetime fields in SQL Server database tables (left over from SQL Server 2005 support) to datetime2. This mitigates an error which can occur when a database field is set to an out of range date time value.
  • Fix: Issue where manual poll URL is displayed when creating a new non-manual polling repository.

  • Enhancement: File include and exclude patterns on repository triggers are now validated on save to ensure that they are valid regular expressions.
  • Enhancement: A CommentHTML property has been added to changeset expression objects and changeset notification model variables. If an issue connector is configured, this will contain the changeset comment text with any issue IDs replaced with with HTML links.

  • Some third party package updates.

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


October 8th, 2019


  • Fix: The new "Wait for completion" property was not set to true for existing PowerShell actions.
  • Update: Installer now removes extra files left over from previous installations.
  • Update: PostgreSQL database provider upgraded to version 4.1.1.

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


October 2nd, 2019


  • Feature: New FinalBuilder action settings to support new export log styles and themes added to version of FinalBuilder.
  • Feature: Feature: Added property collector for .Net Framework 4.8.

  • Fix: The wrong manual poll URL, from the previous repository that was edited, was being displayed in the Edit Repository dialog.
  • Fix: User subscriptions were incorrectly showing on the Subscription page in the Administration section.
  • Fix: Error when using a enumerated values such as log message type in notification templates.

  • Update: The messages in Latest Errors and Warning Messages sections of the build log are no longer included in the ErrorAndWarningLogMessages and TailLogMessages properties, used in expressions and notification templates.

  • Update: Pin comment editing dialog is now pre-populated with existing comment when editing.
  • Enhancement: Improved build logging throughout from agent to server. This should significantly improve build times when using actions with detailed logging.
  • Enhancement: The manual poll URL is now displayed directly after saving a new repository.
  • Enhancement: Type naming and descriptions have been improved in the Available Variables tree on the Notification Template editing page.
  • Enhancement: The values shown when hovering over the bars on the Build Times and Queue Times charts on the Detail View dashboard page are now in days, hours, minutes and seconds, rather than just seconds. Note that the precise time is displayed after hovering over one bar for at least 3 seconds.
  • Enhancement: The service ports can now be specified (and are verified) when running the server installer.

  • Some third party package updates.

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


September 18th, 2019


  • Breaking change: All variable types (not just expression variables) are now escaped when passed to the FinalBuilder command line. This includes splitting array variables into lines and masking protected variables as required.

  • Update: A new "Log File Location" option has been added to FinalBuilder action. This allows you to override the default setting, where the log is written to a temporary folder, to write the log to the working folder where it can be retained via workspace rules and artifact rules for subsequent viewing.
  • Update: Changeset accumulation is now started as soon as a build is created and continues until all conditions are met, if Accumulate Changes is set on any configuration condition.
  • Update: The quiet period waiting period is now written to the build timeline.

  • Fix: Regression bug in where Server.HostUrl server property could be reset to localhost on service start up.
  • Fix: The 'Only notify users who caused the build' option on repository triggers now includes group subscriptions when matching the changeset user with subscriptions. Previously it only included user subscriptions.
  • Fix: Any action state is now reset before executing. This fixes issues with expressions in some fields being cached for XUnit, Mocha, File Transfer, Docker and some Azure actions when running under an iterative action (e.g. For Each, While).
  • Fix: The report count on the build page incorrectly included archived reports.
  • Fix: Possible deadlock when debug logging is enabled.

  • Some minor text updates.
  • Some third party package updates.

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


September 9th, 2019


  • Feature: New python actions:
  • Enhancement: PowerShell action updated to support version PowerShell Core versions 6 and 7.
  • Enhancement: 'Wait for completion' option added to PowerShell action.

  • Enhancement: Added new 'Process.OutputEncoding' and 'Process.OutputCodePage' agent properties which can be used to control the default output encoding when running command line processes on each agent.
  • Enhancement: Added new Process Output Encoding properties (`Encoding Name` and `Code Page`) to the Environment tab of all actions which run a command line. This can be used to override the default output encoding for each action.

  • Enhancement: New default error message patterns to match errors in output from DotNet Build, Publish, Test and Run actions.
  • Enhancement: Added list of Latest Warnings to build log after action output.
  • Enhancement: The output from actions that run a command line process is now wrapped in a "Output" message group in the build log. This is for easier access to Latest Errors and Latest Warnings.

  • Enhancement: Git repositories now allow a blank username. This is required when using a personal access token as the password for some services such as TFS/DevOps.
  • Enhancement: Dotnet Build, Pack, Publish, Restore and Test actions now allow a solution file to be entered for the project path.
  • Enhancement: The 'Browse' button on file input boxes in action settings now lists files from the head of the default branch rather than the tip changeset for each repository.

  • Fix: The list of latest errors messages shown in build log after action output did not include errors picked up using error message patterns.
  • Fix: The build variable value is now used rather then the default configuration variable when expanding the Report Filename field.
  • Fix: The poll url for manual repositories changed to ignore any id sent in the post request content. Previously a id sent by TFS web hook would override the id in the URL.
  • Fix: Correction to default for Maximum Environment Variable Length field on MSBuild action.

  • Upgraded bundled PostgreSQL service to version 9.6.15.
  • Some minor UI updates.
  • Some third party package updates.

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


August 22nd, 2019


  • Feature: Triggers now include User filtering settings allowing inclusion or exclusion of changesets with usernames matching specified patterns.
  • Enhancement: New template editor with syntax highlighting.
  • Enhancement: New reset buttons on template editor to reload saved template.
  • Enhancement: Templates are now validated on save.
  • Enhancement: You can now click on items in the available variables tree to insert a variable name into the template editor.
  • Enhancement: Added a variable dictionary to build notification templates allowing direct access to variables by name {{Variable.VariableName}}. Note that the variable must be scoped so that it is available to all builds which use a notification template.
  • Enhancement: Application variables (in addition to configuration and project variables) can now be updated by triggers.
  • Enhancement: Changes to the stage promotion timeout are now applied retrospectively to existing builds which are waiting for promotion. Note that this a possible breaking change if you have stages waiting for promotion and the timeout has been changed since those builds were run.
  • Enhancement: The project names on the Projects page in the Administration section now link to the project view.
  • Enhancement: Minor improvement to build log performance.
  • Fix: Backslashes can now be escaped in quoted functions parameter. This is to handle issue where an end quote was unintentionally escaped by a preceding backslash. e.g. $Utils.GetString("Folder\\\\SubFolder").Replace("\\\\","\\")$. Note that this a possible breaking change as all backslashes in function parameters now need to be escaped.
  • Fix: Timing issue affecting the operation of the "Skip commits previously built for this configuration" trigger option.
  • Fix: Error with Subversion repository when upgrading from an earlier version where the "Host mismatch" trust invalid certificates option was selected.
  • Fix: Javascript error loading subscription with no source (where a project or configuration has been deleted).
  • Fix: Installers now handle a domain specified as a dot (for local users).
  • Upgrade: Updated some third party packages.
  • Some minor UI updates

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


August 1st, 2019


  • Fix: Changes to property collectors were reverted to default on service startup.


July 31st, 2019


  • Fix: Error about missing NuGet.Core assembly when running NetCore property collector on fresh installation.
  • Fix: Changed internal implementation of repository rule patterns to avoid third-party limitation on number of rules.
  • Feature: Added ‘pinBuild’, ‘unPinBuild’, ‘tagBuild’ and ‘removeBuildTag’ message types for use with custom log messages.
  • Feature: Added proxy settings to Git repositories.
  • Enhancement: Added maximum length validation to stage workspace, repository and artifact rules text areas.
  • Enhancement: Minor UI tweaks.
  • Upgrade: Bundled Mercurial command line used for repository caches upgraded to version 5.0.2.
  • Upgrade: Updated some minor third party packages.

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


July 23rd, 2019


  • Fix: Build would not start if a custom path was used for an action installer (e.g. NuGet for XUnit action, or NPM for Grunt action).
  • Fix: Double $ and % characters in literal parameter values for expression functions are now unescaped before evaluating. e.g. $Utils.GetString("$$999").Replace("$$", "£")$.
  • Enhancement: Updated forms to ensure that browser auto-fill does not interfere with suggestion list on password fields in 'show password' mode.
  • Enhancement: Updated forms to prevent browsers from attempting to auto-fill non-username fields with usernames.
  • Enhancement: Unit test messages are now displayed as HTML and stack trace is not displayed if it is the same as the message.
  • Feature: Added a 'For Each Directory' action which can be use to run child actions on a list of directories matching a set of patterns.
  • Enhancement: Improvements to argument masking in build log.
  • Enhancement: Additional error handling and messages.
  • Upgrade: Updated some third party packages including the PostgreSQL data provider.

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


July 2nd, 2019


  • Update: Iterable actions, e.g. (For Each, For Each File and While), now include an option to write the value of the current item to the build log. This option is enabled for new actions by default.
  • Update: Notifications and build event handler expressions now have access to the last fifty build log messages, and all error and warning messages. The expressions $Build.TailLogMessages$ and $Build.ErrorAndWarningLogMessages$ can be used in build event handlers, and the variables TailLogMessages and ErrorAndWarningLogMessages can be used in Build Discarded, Build Error, Build Failed, Build Fixed, Build Stopped, Build Success, Build Promoted To Next Stage, Build Awaiting Stage Promotion and Build Stage Promotion Cancelled notification templates.
  • Update: The installer now automatically grants the service user full control of the service configuration file. This is required for storing unique encryption keys on first run.
  • Fix: It was possible for an LDAP user to log in without being a member of any linked group. Note however that the user would not have had access to view or modify any projects, configurations or settings.
  • Fix: A newly started agent can no longer start a build before property collection is complete.
  • Fix: The NuGet actions were not showing the correct settings according to the version that was selected.
  • Fix: Failure to set a variable in iterable actions is now caught correctly by Try andCatch actions.
  • Fix: Running stage blocks were sometimes displayed vertically on the configuration activity view.
  • Update: Minor UI fixes.

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


June 20th, 2019


  • Fix: Json encoding error when editing notification templates.
  • Fix: Default MSBuild property collector for MSBuild 6.0 was set to version 5.0.
  • Fix: Stage previous duration was not always calculated causing incorrect display of stage progress bar.
  • Fix: Cached user details were not being invalidated when updating user preferences.
  • Update: Added filtering the Server Properties, Agent Properties and Property Collectors pages in the Administration section.
  • Update: Added link button to export build history as XML.
  • Update: Third party packages upgraded.
  • Update: Minor UI fixes.

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

v1.9.1.191 Release Candidate

June 12th, 2019


  • Fix: Reverted breaking change where $Source.RepoName.BuiltChangeset.Id$ was no longer the same as $Source.RepoName.BuiltChangeset.RepositoryChangeId$.
  • Update: Added Plan and Resource Group parameters to Azure Upload Web App action.
  • Update: Variables can now be extracted from the output of the Azure Upload Web App action.
  • Update: All the NuGet actions have been updated to support all the latest command line options.
  • Update: We have added a new Nuget Sign action.
  • Update: PostgreSQL has been upgraded to version 9.6.13. Note that the PGAdmin 3 tool is no longer installed. We recommend downloading PGAdmin 4 for accessing the database. PGAdmin 4 has now improved significantly since the first edition.
  • Update: Third party packages, including data access components and emailer, upgraded.
  • All updates and fixes added to v1.9.0.451 are included in this release.

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

v1.9.1.169 Beta

April 30th, 2019

Note on Betas: Beta versions include significant changes which are still undergoing final testing before an official release. While we don't anticipate any issues running our beta versions, they have only been tested in our environment and there may be bugs that we have not yet discovered. We therefore recommend that you install a beta version on a staging server to test that it will not cause you any problems, or wait until an official release, before installing to a production server.

Should you encounter any bugs or other issues with a Beta version, please contact us via

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

New Version 1.9.1 Features

Enhanced Expressions Engine

We have made substantial improvements to the expressions engine including function return types, chaining of functions, nesting functions as function parameters, selection and filtering of collections and many improvements to expression parsing. We have also added several new expression objects and functions.

Stage Editor Changes

The action list has been redesigned to allow more actions and categories. Stage icons now expand to fit the text content.

New Premium Deployment Actions

We have added a set of premium actions which can be used for deploying the results of your build. These actions provide support for Docker, Azure, SQL packages, File Transfer and SSH. Note that these actions can only be used if you have purchased one or more concurrent build licenses.

Other Actions

We have added an Extent Reports action and updated the ReportGenerator action to include all the latest commands. We have also included a Rename Directory action

Automatic Reporting

We have added a new option to some actions (FinalBuilder, ReportGenerator and the new Extent Reports action) to automatically register generated reports with the server.

This version also builds upon all the fixes and improvements in version 1.9. Any further bug fixes and improvements on version 1.9 will be merged into version 1.9.1

See Introducing Continua CI Version 1.9.1 Beta for further details on the new features.