BuildMaster 4.8.5 Has Been Released

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

  • BM-1910 - FIX: Transfer Files action should always copy modified timestamp value
  • BM-1909 - Allow background server check trigger on Server Overview page to be disabled
  • BM-1908 - Allow option to enforce server environment associations at deployment time
  • BM-1907 - Wrap long application names without spaces or dashes on Application Overview page so they do not appear beneath the environment boxes
  • BM-1873 - FIX: Changing release on Import Build does not update build importer defaults
  • BM-1887 - Force release number selection when creating a new build when there are multiple active releases and the context for creation is not already in a release
  • BM-1888 - FIX: Issue details should show who created the issue
  • BM-1892 - Increase database change script max name length to 250 characters
  • BM-1894 - FIX: Assign unique HTML ID to login page form fields so that browser password managers can remember the password
  • BM-1896 - FIX: Deployable variables should only be allowed to be added when editing the deployable
  • BM-1897 - FIX: Manual configuration file deployment page should not display restricted instance environments
  • BM-1898 - FIX: File System Build Importer does not respect the file mask set in the template
  • BM-1899 - Display the issue tracker issue ID on the Issues Overview page instead of the incremental ID
  • BM-1900 - Add "Do not Execute option" on Promote Build Page
  • BM-1901 - FIX: An imported deployable's artifact cannot be deployed unless there was at least 1 promotion for the build containing that artifact when "UseFurthestBuildForImportedDeployable" option is set to tru
  • BM-1903 - Clarify "scheduled to occur in the future" message when the execution has not started at its scheduled time
  • BM-1905 - FIX: Release Closed event listener should subscribe to the Release Deployed event instead of the Build Promotion Completed event
  • BM-1906 - Performance improvements to some pages that call Release_GetReleases in the SQL API

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