VSoft Technologies BlogsVSoft Technologies Blogs - posts about our products and software development.https://www.finalbuilder.com/resources/blogsAnnouncing the Release of Continua CI Version 1.9.2https://www.finalbuilder.com/resources/blogs/postid/840/introducing-the-release-of-continua-ci-version-192Continua CI,DelphiMon, 09 Nov 2020 06:16:32 GMT<p>We are delighted to announce that <a href="/downloads/continuaci/continua-ci-version-history-v192" target="_blank">version 1.9.2 of Continua CI</a> has passed through the beta and release candidate stages, and has now been released. Here is a reminder of the new features in v1.9.2:</p> <ul> <li><a href="#export-and-import"><b>Export and Import</b></a>: You can now export one or more configurations to a file and import them back from the file into Continua CI.</li> <li><a href="#requeuing-stages"><b>Requeuing Stages</b></a>: Requeue a failing stage without restarting the build.</li> <li><a href="#multiple-daily-cleanup-rules"><b>Multiple Daily Cleanup Rules</b></a>: Each type of build by-product can now have a different shelf life.</li> </ul> <h2><a name="export-and-import">Export and Import</a> <a class="up-link" href="#" title="Go to top"><img src="/images/up-icn.png" /></a></h2> <p>Users with Configuration Edit permissions can now export one or more project configurations to a YAML or JSON file. This may be for backup, versioning or migration to another server.</p> <p>The export wizard has a number of steps allowing selection of one or more configurations, and also any related repositories, variables and shared resources.</p> <p><img alt="Export Wizard - Configuration Selection" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Export_Resized.png" /></p> <p>The configuration details can be exported to YAML or JSON file formats, according to your preferences for readability and differencing.</p> <p><img alt="Export Wizard - File Details" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Export-File-Details_Resized.png" /></p> <p>The resultant file is downloaded to your computer, allowing you to file it away until you need it.</p> <p><img alt="Export Wizard - Downloaded File" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Export-Download.png" /></p> <p><img alt="Export Wizard - YAML" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Export-YAML.png" /></p> <p>The import wizard also consists of several steps, allowing users with Project Edit permissions to upload a file, ...</p> <p><img alt="Import Wizard - File Selection" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Import-File-Details_Resized.png" /></p> <p>choose which items in the file to import and whether to overwrite any existing matching items of create new items.</p> <p><img alt="Import Wizard - Configuration Selection" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Import-Configurations_Resized.png" /></p> <p>The import runs in a transaction, so if any modified file content fails validation it will rollback...</p> <p><img alt="Import Wizard - Import Failed" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Import-Failed_Resized.png" /></p> <p>allowing you to make changes and retry.</p> <p><img alt="Export Wizard - Import Complete" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Import-Complete_Resized.png" /></p> <h2><a name="requeuing-stages">Requeuing Stages</a> <a class="up-link" href="#" title="Go to top"><img src="/images/up-icn.png" /></a></h2> <p>Sometimes a build stage may fail due to external influences. It could be that a file server was offline, network connectivity was down, or a file was locked for access. If it has taken several long stages to get to this point, then having to run the whole build again from the start can be a pain.</p> <p>The last stage of a completed build can now be requeued, providing that it has failed, stopped or errored, and the server workspace is intact.</p> <p>If no parts of the server workspace have been removed by the cleanup process, then a Requeue Stage button will be shown after the last stage in the Stages list on the Build page.</p> <p><img alt="Action list categories" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Requeue-stage-button.png" /></p> <p>This allows you to requeue and execute the stage again!</p> <p><img alt="Action list search" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Requeue-stage-running.png" /></p> <p>You can also optionally make changes to the stage actions and requeue the stage with the latest changes.</p> <p><img alt="Stages" class="dropShadow" src="/blogimages/daves/v1.9.2-release/Requeue-stage-dialog.png" /></p> <h2><a name="multiple-daily-cleanup-rules">Multiple Daily Cleanup Rules</a> <a class="up-link" href="#" title="Go to top"><img src="/images/up-icn.png" /></a></h2> <p>Every build that is executed within Continua CI stores information in the server's workspace, such as artifacts and build logs, and entries in the database. These by-products are vital for executing your build process and tracking build information, however, they can also take up considerable disk space over time and have a negative impact on database performance. The cleanup settings define the shelf life for the build by-products.</p> <p>Up until now, the cleanup settings have been quite limited - you could set up a single policy per configuration defining the build age and build limits for cleaning up either the database, the workspace, or both. Often, however you would want to cleanup the workspace files to save space, well before removing the build from the database. This update allows you to define multiple cleanup rules, with different shelf lives for each type of build by-product.</p> <p><img alt="Cleanup rules" class="dropShadow" src="/blogimages/daves/v1.9.2-release/CleanupRules_Resized.png" /></p> <p>Each rule can include one or more by-product to clean up.</p> <p><img alt="Cleanup rules dialog" class="dropShadow" src="/blogimages/daves/v1.9.2-release/CleanupRule.png" /></p> <p>Download the installers for Continua CI v1.9.2 from the <a href="/downloads/continuaci" target="_blank">Downloads</a> page</p> <style type="text/css">ul.horizontal { overflow: auto; margin: 10px 0 0 0; } ul.horizontal li { float: left; margin-left: 2em } .syntaxhighlighter { background-color: #eee !important; margin-top: 0 !important; padding: 10px; outline-style: dashed; outline-width: 1px; outline-color: #666; width: 97% !important; } .syntaxhighlighter .line.alt2 { background-color: #eee !important; } .syntaxhighlighter table td.code { overflow-y: hidden !important; } .syntaxhighlighter .plain, .syntaxhighlighter .plain a { color: #639099 !important; } h1 { margin-bottom: 0.6em !important; } .up-link { float: right } img.dropShadow { -webkit-filter: drop-shadow(5px 5px 5px #222); filter: drop-shadow(5px 5px 5px #222); margin-bottom: 1em; } </style> 840Introducing Continua CI Version 1.8.1https://www.finalbuilder.com/resources/blogs/postid/748/introducing-continua-ci-version-181Continua CIThu, 08 Sep 2016 16:43:33 GMT<br /> <br /> <br /> <p>This version adds several back-end performance enhancements including significant improvements to database query caching. We have also updated various third party packages and upgraded the bundled PostgreSQl database from version 9.3.4 to version 9.5.3. What&rsquo;s more, this release builds upon all the improvements and fixes made to version 1.8.</p> <h2> New Actions</h2> <br /> <p>To keep up with the latest developments in Visual Studio, we have added several new actions for working with .Net Core projects. The DotNet Build, DotNet Pack, DotNet Publish, DotNet Restore, DotNet Run and DotNet Test actions all run the DotNet Cli command line.</p> <p><img alt="DotNet Build Action" src="https://www.finalbuilder.com/blogimages/daves/v1.8.1/DotNetBuildAction.png" /></p> <p>This release also includes a new action for importing XUnit tests from an XML report file. The sort of file you may choose to output from the DotNet Test action.</p> <p>To polish this off we have added new NPM Pack and NPM Publish actions for sharing your completed packages.</p> <h2> New Build Event Handlers</h2> <br /> <p>A powerful new addition to the Continua CI build event handlers is the HTTP Request handler which allows you to send JSON or XML to HTTP endpoints via GET, POST. PUT, DELETE, PATCH methods and extract values from the results to set as Continua CI variables.</p> <p><img alt="HTTP Request Build Event Handler" src="/blogimages/daves/v1.8.1/HTTPRequestBuildEventHandler.png" /></p> <p>This enables interaction with a various existing web services and REST APIs. You could, for example, use this feature to send a message via Slack when a build starts, tag a commit on GitLab when a build finishes or even translate a variable value to Azerbaijani using Google Translate API. If you have any in-house web services which handle HTTP requests, it is likely that these can be accessed too.</p> <p>We have also added a new GitHub Release build event handler for creating, updating and deleting GitHub releases. This also allows you to upload artifacts as GitHub release assets.</p> <h2>Other New Features</h2> <br /> <p><strong> Build Event Handler conditions</strong>. You can now control the triggering of handlers based on the value of build variables or expression objects. These values may be specified when queuing a manual build or set in the stage workflow. You could, for example, only send a GitHub Release if the number of failed unit tests $Build.Metrics.UnitTests.Failed$ is zero.</p> <p><img alt="Build Event Handler conditions" src="/blogimages/daves/v1.8.1/BuildEventHandlerConditions.png" /></p> <p><strong>Continue on failure.</strong> Builds can now be set to progress to the next stage after one stage has failed. Stage gates now include an $Stage.IsSuccessful$ condition by default. This can be removed to allow the build to continue to the next stage when a stage fails. So you can see what failed, the stages are now coloured green or red in Tile and Details dashboard views to indicate an success or failure status.</p> <p><img alt="Continue on failure" src="/blogimages/daves/v1.8.1/ContinueOnFail.png" /></p> <p><strong> New cleanup options.</strong> We have also made some changes to the server cleanup policy, giving you the options to clean up build statistics. The database category has also been split up so that build unit tests can be cleaned up without cleaning up the full build. This is important to prevent database tables growing too large when you have a large number of unit tests.</p> <p><img alt="Cleanup options" src="/blogimages/daves/v1.8.1/CleanupOptions.png" /></p>748Continua CI 1.8 Releasedhttps://www.finalbuilder.com/resources/blogs/postid/745/continua-ci-18-releasedContinua CIThu, 14 Apr 2016 13:07:29 GMT<p> <br /> <br /> </p> <p>We are pleased to announce that Continua CI 1.8 has been released. It was actually released a couple of days ago, but for anyone who missed it, here is a heads up with and overview of the new features. We'd also like to thank all those who downloaded the beta - the time and effort spent reporting issues helped us to fix some important bugs and is most appreciated.</p> <p>Version 1.8 adds the following features which build upon all the improvements and fixes made to version 1.7.1.</p> <h2>Dashboard Filtering</h2> <br /> <p>We've added a new filter box to the dashboard so you can quickly find the configuration (or project) that you are looking for as you type. Use the shortcut key F on the dashboard pages to focus on the filter box and start typing.</p> <p><img alt="Dashboard filtering" src="/blogimages/daves/v1.8/DashboardFiltering.png" /></p> <br /> <h2>Shared Resources</h2> <br /> <p>Many of you have requested more control over the number of builds which can run concurrently for some configurations. This may be to restrict the number of times a particular tool is run due to a license, memory or processor limit, or to prevent concurrency issues with multiple build stages simultaneously writing to the same file, folder or network resource.<br /> You can now allocate quotas to named Shared Resources and specify that builds and stages must acquire a lock on the Shared Resource before running. If all locks are allocated, then the build or stage will wait on the queue until a lock is released.</p> <p>Shared resources can be associated with the server or a particular agent in the Administration pages.</p> <p><img alt="Agent shared resources" src="/blogimages/daves/v1.8/AgentSharedResources.png" /></p> <p>Agent shared resources are acquired when selecting an agent to run a stage. Continua will select the agent with the largest available quota of each shared resource.</p> <p><img alt="Stage shared resource locks" src="/blogimages/daves/v1.8/StageSharedResourceLocks.png" /></p> <p>Server shared resources can also be acquired when selecting an agent, or while on the build queue after evaluating configuration conditions.</p> <p><img alt="Shared resource lock configuration condition" src="/blogimages/daves/v1.8/SharedResourceLockCondition.png" /></p> <p>We hope you find that shared resources can provide many different ways to control the build process.</p> <br /> <h2>Requeue Build</h2> <br /> <p>Sometimes a build may fail due to an offline network resource, or some logical error in the stage workflow. Up until now, your only option was to re-run a build for the same branch heads. If any new changesets had been committed to the branch since that build, then you are out of luck.</p> The new Requeue Build button on the Build View page allows you to requeue an existing build using the same changesets, variables and queue options. Any changes to the configuration such as stage actions or repositories are taken into account and used for the new build. <p><img alt="Requeue build button" src="/blogimages/daves/v1.8/RequeueBuildButton.png" /></p> <p>You can also change the priority, comment and variables before requeuing the build.</p> <p><img alt="Requeue build options menu item" src="/blogimages/daves/v1.8/RequeueBuildOptionsMenuItem.png" /></p> <p>Clicking on the &ldquo;Build requeue options&rdquo; menu item will open the Queue Options dialog.</p> <p><img alt="Requeue options dialog" src="/blogimages/daves/v1.8/RequeueOptions.png" /></p> <br /> <h2>Persist Build Variables</h2> <br /> <p>Another common request has been to persist variable values from one build to another build. This may be to keep a count of builds on a particular branch or to flag that some actions have been completed in one build and do not need to be repeated.</p> Continua CI takes a copy of configuration and project variables at the start of each build. These copies are referred to as build variables. Any changes to build variables are normally discarded when the build finishes and cannot be used by other builds. <p><img alt="First tab of Persist Build Variable build event handler dialog " src="/blogimages/daves/v1.8/PersistBuildVariable1.png" /></p> <p>The new Persist Build Variable build event handler allows you to save the value of the build variables when specific events happen in the build timeline. This is stored as the value of the configuration variable. Subsequent builds will then pick up this revised value and use it as the initial value of the build variable.</p> <p><img alt="Second tab of Persist Build Variable build event handler dialog " src="/blogimages/daves/v1.8/PersistBuildVariable2.png" /></p> <p>As Continua CI allows multiple builds to run concurrently, it is important to control when the variables are overwritten. A later build may run faster and finish before a build which started earlier, causing unexpected results. &nbsp;You can optionally state that a variable should not be persisted if the configuration variable has been modified (e.g. by another build) since a specified build event, such the build start.</p> <p><img alt="Options tab of Persist Build Variable build event handler dialog " src="/blogimages/daves/v1.8/PersistBuildVariable3.png" /></p> <p>You can also prevent concurrency issues by using this feature in conjunction with shared resource locks.</p> <br /> <h2>Other New Features</h2> <br /> <ul> <li>You can now set the Variables display order of variable prompts on the Queue Options dialog.</li> <li>We have provided buttons for cloning Triggers, Repositories and Build Event Handlers.</li> <li>Configuration Conditions can now be disabled.</li> <li>All actions which run external processes now have a Timeout (in seconds) setting.</li> <li>We have also added a new <a href="http://cakebuild.net/" target="_blank">Cake </a>build runner action and a new <a href="https://msdn.microsoft.com/en-us/library/jj155796.aspx" target="_blank">VSTest</a> unit testing action.</li> </ul>745Automise 5 Betahttps://www.finalbuilder.com/resources/blogs/postid/741/automise-5-betaAutomiseWed, 20 Jan 2016 13:06:13 GMT<p>Today we are delighted to release the Automise 5 BETA, which contains our new Stepping Engine and Action List Dependencies as the headline features. </p> <p>For five years we have updated and improved Automise 4 through our continuous delivery cycle.&nbsp;This has worked well. Allowing for improvements to actions (like FTP\SFTP\FTPS suite) to come out gradually and consistently. Allowing everyone to pick and choose at which point to take feature updates.</p> <p>The Automise 5 signals a major "tick" to this regular flow of updates. The majority of these updates are at the core of what Automise does to solve your automation challenges.</p> <h2>What's new in Automise 5</h2> <h3>Stepping Engine</h3> <p>We have undertaken a major rewrite of the internal stepping engine for Automise 5. This has reduced the moving parts, while also enabled extra features to be implemented. In the end this will mean your projects will run faster, consume less resources, while also providing some extra tools for debugging projects.</p> <h3>Action List Dependencies</h3> <p>Action Lists now allow for listing of other Actions Lists they are dependent on. Dependencies are always run before the action lists which depend on them. For example this allows specifying a UploadAndClean Action List that depends on the Clean and Upload Action List. When <span>UploadAndClean</span> is run, if the Clean and Upload Action Lists have not been run they will be.</p> <p style="text-align: center;"><img alt="Action List Dependencies" src="/blogimages/jason/Automise5-beta-release/at5_actionlist_dependencies.png" style="text-align: center;" /></p> <h3>Step into included projects</h3> <p>Due to the previous version of the stepping engine stepping into included projects was not possible. Instead the user had to wait for the included project to complete before continuing with debugging. Stepping into included projects with Automise 5 will now open the included project, and continue stepping from inside the included project.</p> <h3>Breakpoint Conditions</h3> <p>Another addition to the debugging experience is breakpoint conditions. These allow stopping the executing of a script at a certain point in time. Conditions can be a number of passes over the breakpoint, or when a variable equals a certain value.</p> <p style="text-align: center;"><img alt="Action List Dependencies" src="https://www.finalbuilder.com/blogimages/jason/Automise5-beta-release/at5_breakpoint_properties.png" style="text-align: center;" /></p> <h3>IDE Themes (Light and Dark)</h3> <p>After five years we thought it was time Automise got a new coat of paint. We have implemented two new themes, a light and dark theme (defaulting to the dark on first run up).</p> <table style="border: none; width: 100%;"> <tbody> <tr> <td style="width: 50%;"> <img alt="Action List Dependencies" src="https://www.finalbuilder.com/blogimages/jason/Automise5-beta-release/at5_dark_theme.png" style="text-align: center;" /> </td> <td style="width: 50%;"> <img alt="Action List Dependencies" src="https://www.finalbuilder.com/blogimages/jason/Automise5-beta-release/at5_light_theme.png" style="text-align: center;" /> </td> </tr> </tbody> </table> <h3>Action List Out Parameters</h3> <p>Action Lists now allow for retrieving any number of values from them. A variable assigned to the out parameter on the Action List will be given the value of that parameter when the Action List has completed. This will allow for more Action Lists that generate values for use else where in the Automise Project.</p> <h3>Project Formats</h3> <p>Since the start of Automise the project files have used XML for their structure. As Automise has grown, so too have the elements in the projects XML file. This has placed more strain on those left to diff versions of Automise projects.</p> <p>To aleavate this challenge Automise 5 has introduce two major updates to the Automise project file structure.</p> <p>&nbsp; &nbsp;1. A new DSL project file format (the new default format)</p> <p>&nbsp; &nbsp;2. A new XML project file format</p> <p>The new Automise DSL structure is concise, and very simple to diff.</p> <pre class="brush:delphi; toolbar:true;">project begin projectid = {04710B72-066E-46E7-84C7-C04A0D8BFE18} Action List begin name = Default Action Listid = {E6DE94D6-5484-45E9-965A-DB69885AA5E2} rootaction begin action.group begin id = {D860420B-DE46-4806-959F-8A92A0C86429} end end end end </pre> The new Automise XML structure is a great deal less verbose than the older format. <pre class="brush:xml; toolbar:true;">&lt;?xml version="1.0" encoding="UTF-8"?&gt; &lt;Automise&gt; &lt;project&gt; &lt;projectid&gt;{6A717C24-D00F-4983-9FD0-148B2C609634}&lt;/projectid&gt; &lt;Action List&gt; &lt;name&gt;Default&lt;/name&gt; &lt;Action Listid&gt;{E6DE94D6-5484-45E9-965A-DB69885AA5E2}&lt;/Action Listid&gt; &lt;rootaction&gt; &lt;action.group&gt; &lt;id&gt;{D860420B-DE46-4806-959F-8A92A0C86429}&lt;/id&gt; &lt;/action.group&gt; &lt;/rootaction&gt; &lt;/Action List&gt; &lt;/project&gt; &lt;/Automise&gt; </pre> <p>&nbsp;</p> <h3>New Actions</h3> <p>Not much to report here, most of the focus has been on the Stepping engine and the IDE. We do have some updates to AWS EC2 and Azure in progress, they will most likely be added in an update when they are ready.&nbsp;</p> <h3>How do I get the Beta?</h3> <span>Links to the beta downloads will be published to the&nbsp;</span><a href="https://www.finalbuilder.com/downloads/automise">Automise Downloads</a><span>&nbsp;page.&nbsp;</span> <h3>What if I find a bug?</h3> <span>Email support (please added Beta to the subject). When reporting an issue, be sure to include the beta build number and details about your environment. Please test with the latest beta build before reporting bugs.&nbsp;</span><br /> <br /> <span>We are particularly keen for people to load up their existing projects from older (ie 4 or earlier) versions of Automise, save them in AT5 format, and load them again and confirm that everything loaded ok.&nbsp;</span><br /> <br /> <h3>When will it be released?</h3> <h3></h3> <span>When it's ready ;) Seriously, though, we expect the release to happen in the next few weeks. Automise 5 is based on FinalBuilder 8, which has been out for several months now and is quite stable.&nbsp;</span>741Continua CI Version 1.7 releasedhttps://www.finalbuilder.com/resources/blogs/postid/734/continua-ci-version-17-releasedContinua CISun, 23 Aug 2015 16:20:37 GMT<p>Version 1.7 of Continua is now released. A big thank you to all those who downloaded the beta and especially those of you who reported issues and bugs.</p> <p> This version introduces several new features, many of which have been requested by users over the past few months. These features are built upon the various improvements and bug fixes applied in revisions to version 1.6. Please don&rsquo;t dismay if your requested feature is not included yet, it is still high on our to-do list. Indeed we have several other features specced out, and some partially developed in the background.</p> <h2>Version 1.7 Features</h2> <h3>New Builds View dashboard</h3> <p>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.</p> <p><img alt="" src="/blogimages/daves/v1.7beta/buildsview.png" /><br /> <br /> </p> <h3>New panel of indicators</h3> <p>Some important numbers including the total count of queued and running builds, as well as available agents and concurrent build licenses.</p> <p><img alt="" src="/blogimages/daves/v1.7beta/indicators.png" /><br /> <br /> </p> <h3>New Repositories tab</h3> <p> This is accessed via the Configurations view and shows status of each repository. We've also included &ldquo;Check &nbsp;Now&rdquo; buttons for immediately polling each repository. You can also initiate repository checking from all existing repository pages</p> <p><img alt="" src="/blogimages/daves/v1.7beta/repoview.png" /><br /> <br /> </p> <h3>Project-wide and configuration versioning options.</h3> <p>We've added some new options in the details section of the project and configuration wizards</p> <ul> <li><strong>Project-wide versioning: </strong>The build version number can now be incremented across many configurations within a project.<br /> <br /> </li> <li><strong>Build number re-use: </strong>A new <span>option at the&nbsp;</span>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. &nbsp;<br /> <br /> </li> </ul> <p> <img alt="" src="/blogimages/daves/v1.7beta/projectwidesettings.png" /><br /> <br /> </p> <h3>Improvements to Build Completed triggers.</h3> <ul> <li><strong>Variable expressions: </strong>You can now use expressions when defining variables allowing you to pass information from triggering to triggered build.<br /> <br /> </li> <li><strong>New conditions tab:</strong> This allows you to use expressions to control whether a build is triggered<br /> <br /> </li> </ul> <p> <img alt="" src="/blogimages/daves/v1.7beta/buildcompletedconditions.png" /><br /> <br /> </p> <h3>Improvements to Repository triggers.</h3> <ul> <li><strong>Trigger on specific file change types: </strong>Triggers can now be set to start only when the changeset contains certain types of file changes e.g. additions, modifications and deletions.<br /> <br /> </li> <li><strong>Trigger file pattern: </strong>You can now specify a file pattern for repository triggers to restrict triggering only to changesets containing matching files.<br /> <br /> </li> <li><strong>Trigger comment pattern:&nbsp;</strong>You can also limit triggering to changesets with specific text in the comment.<br /> <br /> </li> </ul> <p> <img alt="" src="/blogimages/daves/v1.7beta/repotriggeroptions.png" /><br /> <br /> </p> <h3>Other build features</h3> <ul> <li>New <strong>force repository check</strong> option in queue build dialog allowing control over whether to recheck repository when building. There is also a default setting for each configuration<br /> <br /> </li> <li>Improvements to <strong>Stop Build buttons on dashboard view</strong>&nbsp;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.</li> </ul> <br /> <h3>Actions and event handlers</h3> <ul> <li>New <strong>node.js actions </strong> <ul> <li>Package management with Npm and Bower</li> <li>Grunt and Gulp build runners</li> <li>Unit testing with Mocha<br /> <br /> </li> </ul> </li> <li>New build event handler for posting <strong>status updates to a Stash server</strong><br /> <br /> </li> <li>Log Entry action now allows you to <strong>add the message as a build comment</strong>. This can be useful for showing additional build details on the build view page.<br /> <br /> </li> <li>New <strong>comments field </strong>on all actions &ndash; displayed as a tooltip in Stages editor.<br /> <br /> </li> <li>New ContinuaCI.* <strong>system environment variables</strong> are now available to all executable actions.<br /> <br /> <table style="width: 300px;"> <tbody> <tr> <td style="font-family: 'Courier New', Courier, monospace; font-size: x-small;">ContinuaCI.AgentProperty.*<br /> ContinuaCI.Variable.*<br /> ContinuaCI.Project.Name<br /> ContinuaCI.Configuration.Name<br /> ContinuaCI.Build.Id<br /> ContinuaCI.Build.BuildNumber<br /> ContinuaCI.Build.ChangesetCount<br /> ContinuaCI.Build.ChangesetRevisions<br /> ContinuaCI.Build.ChangesetTagNames <br /> ContinuaCI.Build.ChangesetUserNames <br /> ContinuaCI.Build.Elapsed <br /> ContinuaCI.Build.HasNewChanges<br /> ContinuaCI.Build.IsFeatureBranchBuild<br /> </td> <td style="font-family: 'Courier New', Courier, monospace; font-size: x-small;"> ContinuaCI.Build.IssueCount<br /> ContinuaCI.Build.LatestChangeset.Created<br /> ContinuaCI.Build.LatestChangeset.IssueCount<br /> ContinuaCI.Build.LatestChangeset.RepositoryName<br /> ContinuaCI.Build.LatestChangeset.Revision<br /> ContinuaCI.Build.LatestChangeset.TagCount<br /> ContinuaCI.Build.LatestChangeset.UserName<br /> ContinuaCI.Build.Started<br /> ContinuaCI.Build.StartedBy<br /> ContinuaCI.Build.TimeOnQueue<br /> ContinuaCI.Build.UsesDefaultBranch<br /> ContinuaCI.Build.Version<br /> </td> </tr> </tbody> </table> <br /> <br /> </li> <li>Execute Program, DOS Command and PowerShell actions now include an option to generate a <strong>context XML file</strong>. This file contains details of the build including repositories, changesets and files for you to parse with your own script or program.</li> </ul> <br /> <br /> <h3>Git repositories</h3> <ul> <li><strong>Case-only renames</strong> are now recorded in the repository cache.<br /> <br /> </li> <li>New option to list <strong>author instead of committer</strong> as changeset username</li> </ul> <br /> <br /> <h5><strong>Version 1.7 is ready for you to <a href="https://www.finalbuilder.com/downloads/continuaci">download</a> and install. All feedback is welcome!</strong></h5>734Continua 1.5 releasedhttps://www.finalbuilder.com/resources/blogs/postid/721/continua-15-released.NET,Continua CI,GeneralTue, 09 Sep 2014 11:13:57 GMT<br /> <br /> <h2>Continua Version 1.5 is now <a target="_blank" href="https://www.finalbuilder.com/downloads/continuaci">available for download</a></h2> <p>Today marks a milestone in Continua CI as we release version 1.5 of the product. Its been many months in the making, we hope you enjoy the update as much as we enjoyed making it.</p> <p>There are many features that we think you'll benefit from by updating to v1.5, some of these include: </p> <h3>Reworked UI:</h3> <ul> <li>Now using bootstrap framework for styling</li> <li>Redesigned <a target="_blank" href="http://wiki.finalbuilder.com/display/continua/dashboards">dashboards</a> that show more information including graphs.</li> <li>Added stages information to the Project tile and list views</li> <li>Disabled configurations are now displayed as faded</li> </ul> <br /> <h3>Cloning:</h3> <ul> <li>Can now clone whole projects and clone configurations between projects.</li> </ul> <br /> <h3>Stage Conditions:</h3> <ul> <li>Auto Promote conditions - stages can now use conditions to control whether to auto-promote to the next stage.</li> <li>Skip conditions - you can now provide conditions for skipping stages or disable a stage completely.</li> </ul> <br /> <h3>New Actions:</h3> <ul> <li>Update GitHub Status Action is now deprecated (use event handler instead - see below).</li> <li><a target="_blank" href="http://wiki.finalbuilder.com/display/continua/NuGet+Restore+Action">NuGet restore action</a>.</li> <li><a target="_blank" href="http://wiki.finalbuilder.com/display/continua/Fake+Action">Fake (F#) build runner.</a></li> </ul> <br /> <h3>Repository Tags: (Git, Mercurial and Subversion repositories only)</h3> <ul> <li>Continua CI can now detect and list repository tags.</li> <li>Tags are now displayed in changeset tabs on configuration and build views.</li> <li>Repository trigger can now be set to trigger on tag changes (new tags, edits and deletions) changes).</li> <li>You can now run a build on a <a target="_blank" href="http://wiki.finalbuilder.com/display/continua/Builds#Builds-RepositoryBranch/Tag">tagged changeset</a>.</li> </ul> <br /> <h3><a target="_blank" href="http://wiki.finalbuilder.com/display/continua/Build+Event+Handlers">Build Event Handlers:</a></h3> <ul> <li> Octopus Deploy: Create/Deploy/Promote Octopus Deploy releases. </li> <li> Tag Repository Changesets: Apply tags to a repository changeset (Git, Mercurial and Subversion repositories only) </li> <li> <a target="_blank" href="http://wiki.finalbuilder.com/display/continua/Update+GitHub+Status">Update GitHub Status: replaces the Update GitHub Status action</a>.</li> </ul> <br /> <h3>and many more changes including:</h3> <ul> <li> Styling changes for improved handling on small screen sizes</li> <li> Report ordering: you can choose which one is displayed first on the build view.</li> <li> New expression functions: Utils.NewGuid() and Utils.RandomNumber() can be used for generation of temporary paths for example</li> <li> Additional LatestChangeset object within the repository object with Branch, BranchName, Comment, CommitterUserName, CommitterFullName, Created, FileCount, Id and RepositoryUsername properties to use in expressions</li> <li> Continua now supports DUnitX enhanced Command Line Options</li> </ul> <h2>Updating</h2> <p>Updating to this new release is the same regardless if you are using v1.0.X or a recent build from the beta or release candidate. Simply download the installer and run it, the setup will guide you through the install process. As usual we are available on <a href="mailto:support@finalbuilder.com">support@finalbuilder.com</a> if you run into any troubles.</p> <p>For this release you will need to update both the server and agents.</p> <h2>A word of thanks</h2> <p>The team wishes to thank everyone who has participated in the beta and release candidate stages for this release. Your positive feedback has been invaluable in shaping the features and functionality of the product. Thank you for your continued support.</p>721