BuildMaster 4.1.2 Has Been Released

We just shipped BuildMaster 4.1.2. It's a maintenance release of BuildMaster 4.1 which means that there is minimal risk to upgrading from an earlier 4.1. However, if you're planning to upgrade from a version prior to 4.1, 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 4.1.1 and 4.1.2:

  • BM-1372 - FIX: Deploy release button does not appear with one environment in a loose workflow
  • BM-1371 - Allow release resequencing regardless of release count selected
  • BM-1369 - FIX: Clone application does not propagate configurer profile or transfer files targets for unlinked action groups
  • BM-1368 - Application picker should display application groups on clone application page
  • BM-1367 - FIX: Release deployables dropdowns should have release name instead of release number
  • BM-1366 - FIX: Execute script base action should combine script file path with source directory
  • BM-1365 - Allow null Environment_Id for build artifacts
  • BM-1364 - FIX: ModalHeight on action editor page should not be greater than viewport size
  • BM-1363 - Providers_GetProvider should not throw an error if the provider was not found
  • BM-1361 - FIX: Create and close release triggers should not log an error just because an application does not have an associated issue tracker
  • BM-1360 - FIX: Imported deployable release dropdown should not include canceled releases
  • BM-1359 - FIX: Add download link on updates page and fix styling
  • BM-1358 - FIX: Possible TypeInitializationException with invalid activation code
  • BM-1356 - FIX: Installer crashes trying to update IIS settings on Windows Server 2012
  • BM-1352 - FIX: Transfer Files action does not allow variable servers

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