BuildMaster 4.6.2 Has Been Released

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

  • BM-1761 - API: Add Releases_GetNextReleaseNumber method that returns the expected next logical release number based on the release numbering scheme
  • BM-1760 - Allow release name to be specified in the "Create New Release" action
  • BM-1757 - FIX: Trim server names of spaces on save to prevent possible issues with variable servers in the future
  • BM-1756 - FIX: Create Release should be hidden if "Allow multiple active releases" is unchecked for the application
  • BM-1755 - Do not remove the green plus icon to add variables at specific scopes so that more than one can be created without having to visit the Variables pag
  • BM-1753 - FIX: Re-execute promotion link on Execution Details page opens a modal that is not sized correctly, and it should also be combined with the re-execute page
  • BM-1752 - FIX: Cannot purge release when there are configuration file deployments associated directly with that release
  • BM-1751 - Infobox wording that is shown when there is only a single workflow step does not take into account the build step, and may be confusing
  • BM-1750 - FIX: Server name variables should have spaces trimmed when saved
  • BM-1749 - FIX: Deployable selection when downloading a change script deployment tool from the web application does not generate a change script deployment tool based on that selection
  • BM-1748 - FIX: Set Variable Value action should be an agent-based action
  • BM-1747 - Add support for CTRL+F search in config file editor
  • BM-1746 - FIX: Post-Build Auto-Deploy Step Deletes upon Workflow Property Save
  • BM-1745 - Clarify "Service is OK" message when there is a "cannot connect to database error" directly above it
  • BM-1744 - FIX: Clicking in code editors is kind of funky in IE
  • BM-1742 - FIX: Importing deployment plan from XML ignores actions in action groups that are Shared with other action groups in the system
  • BM-1741 - FIX: Duplicating an application and selecting "Link only action groups" does not link correctly with the source application
  • BM-1738 - FIX: The Create Release page should show an error when attempting to create a release with the same number as one that already exists instead of silently closing the modal
  • BM-1737 - FIX: Selecting "Create new..." in the release dropdown on the Create Build page should stay within the modal page instead of changing the target=parent's window
  • BM-1736 - FIX: Attempting to clone an application with configuration files may fail with "TransformType_Code"-related error message
  • BM-1734 - FIX: Width of Add Script dialog does not scale to a readable size correctly
  • BM-1733 - Allow Server List Variable to be filtered by environments
  • BM-1732 - FIX: Create Release Number should warn about 11+ chararacter release numbers
  • BM-1731 - For custom Create New Application wizards on the New Application page, show the custom extension icon if there is one in place of the default grey question mark
  • BM-1728 - Add alternative suggestion when executing a .lnk or .bat file directly fails with "The specified executable is not a valid application for this OS platform" message
  • BM-1726 - On Create Release page, default the value of the next release to the same value as what "auto-increment" on the workflow would set it to
  • BM-1725 - Link to the Script Repository from the Execute Shell Script and Execute PowerShell Script actions for better visibility
  • BM-1724 - Display list of deployables that are included with the release in the Execution Completed event listener
  • BM-1714 - License can display as invalid if an approval-only user was created and licensed with a previous key that allowed approval-only users, but the newer key does not
  • BM-1711 - Improve rules for active license key selection
  • BM-1710 - Make anonymous deployment plans hidden by default on manage deployment plans page

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