BuildMaster 2.6.1 Has Been Released

We just shipped BuildMaster 2.6.1. It's a maintenance release of BuildMaster 2.6 which means that there is minimal risk to upgrading from an earlier 2.6. However, if you're planning to upgrade from a version prior to 2.6, make sure to read the appropriate upgrade notes.

To install or upgrade, simply download BuildMaster and run the installer.

Here's what we changed between 2.6.0 and 2.6.1:

  • BM-600 - FIX: Logging for provider-based actions isn't wired up
  • BM-599 - FIX: Purge application fails if there are existing reports for that application
  • BM-598 - FIX: Installer adds dependency to SQL Server even if it's not installed
  • BM-597 - FIX: Label field in Get Labeled Action is too small
  • BM-596 - FIX: Source Control Action editors should not verify paths if they contain a variable
  • BM-595 - Browsing for anything using Server Groups doesn't work
  • BM-593 - FIX: Purge Application does not delete Build Schedule Variable Values
  • BM-592 - FIX: Deploying configuration file manually to a server group fails
  • BM-591 - Manual configuration file deployment: add checkbox to force current template, allow selection of release number, and display preview of the file
  • BM-588 - Unable to connect to server messages - not very helpful
  • BM-587 - Allow "0" for AgentUpdaterThrottle to not run updates
  • BM-585 - Add a note to Create Deployable indicating that it will be added to active releases
  • BM-584 - NotImplementedException received when deploying artifact (Mono)
  • BM-583 - Add "Install Extensions" To Type Lists
  • BM-582 - Unzip file action should use a source directory
  • BM-581 - FIX: Scheduled URL-triggered builds overview page says buildmaster.localhost regardless of hostname
  • BM-580 - FIX: Timeline control on release details page orders by Build_Number instead of Sortable_Build_Number
  • BM-517 - For command line action, verify that .exe exists on save

To learn more about how we distinguish between major, minor, and maintenance releases, make sure to check out KB#1059 - When should I update?