BuildMaster 5.3.4 Has Been Released
We just shipped BuildMaster 5.3.4. It's a maintenance release of BuildMaster 5.3 which means that there is minimal risk to upgrading from an earlier 5.3. However, if you're planning to upgrade from a version prior to 5.3, 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 5.3.3 and 5.3.4:
- BM-2182 - FIX: Editing legacy actions only scopes to correct application if the plan existed pre-v5.0 and does not take into account newly added legacy plans
- BM-2181 - FIX: Variables page mistakenly displays variable migration button and legacy declarations when there are exactly 0 variables in the system
- BM-2180 - FIX: Server roles variable editor does not refresh properly after deleting a variable, requiring the entire page to be refreshed
- BM-2179 - Show plan name and pipeline information on the Execution Details page
- BM-2176 - FIX: Create retention policy time parsing generates an error
- BM-2177 - FIX: Legacy Set Variable action does not match v5.3 style package and release variables
- BM-2175 - FIX: Editing an anonymous legacy deployment plan that is unassigned to any applications results in an error when applicationId=0 is included in the query string
- BM-2174 - Improve help text when creating a Private Key credential from the Edit Server page
- BM-2173 - FIX: Change Controls Performed automated gate approval cannot be serialized properly
- BM-2172 - Add XSLT configuration file template type where the XSL stylesheet is the template, and the XML documents are the instances
- BM-2171 - FIX: Infrastructure export error with invalid agent or legacy server group
- BM-2170 - FIX: Infrastructure sync variable export can improperly nest JSON objects if a variable is marked sensitive
- BM-2168 - Add "Legacy" Note to Server Groups
- BM-2169 - Indicate variable type ($,@,%) next to name in Variables Table
- BM-2166 - FIX: Always treat variables that do not start with map/list specifier followed by an opening parenthesis [i.e. %( or @( ] or grave apostrophe as a scalar value
To learn more about how we distinguish between major, minor, and maintenance releases, make sure to check out KB#1059 - When should I update?