BuildMaster 5.2.2 Has Been Released
We just shipped BuildMaster 5.2.2. It's a maintenance release of BuildMaster 5.2 which means that there is minimal risk to upgrading from an earlier 5.2. However, if you're planning to upgrade from a version prior to 5.2, 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.2.1 and 5.2.2:
- BM-2098 - FIX: Add Environment page uses invalid API method internally causing SQL exception
- BM-2093 - FIX: Remove spurious "resource ace/worker-xml.js and/or ace/worker-json.js does not exist in InedoLibWeb" errors from error log
- BM-2087 - FIX: Redeploying always uses plan name of previous execution instead of plan configured in pipeline
- BM-2097 - FIX: Plans_Manage privilege should be required to open plan editor
- BM-2095 - FIX: Legacy transfer files action does not recurse when given a directory with a trailing \
- BM-2094 - FIX: Legacy Execute Shell Script action fails with proxying error
- BM-2089 - FIX: Legacy Promote Build action may not promote all packages
- BM-2090 - FIX: SSH agent temp path is not exposed and defaults to /tmp/buildmaster unless it was converted from a legacy agent
- BM-2084 - Add "Overwrite" Option to CreateArtifact Operation
- BM-2082 - FIX: Legacy server group should not be a link on the Environment Details page
- BM-2078 - Link to "Legacy Plans in BuildMaster 5.0" knowledge base article on the Convert to OtterScript page
- BM-2079 - Only display "Legacy plan variable support" when there are legacy plans
- BM-2074 - FIX: libssh2 native binary directory is not deployed correctly by installer for web application
- BM-2073 - Clarify that UseUniqueExecutionTempDirectory is only for legacy plan executions
- BM-2072 - FIX: Add deployable to all active releases checkbox does not add release deployable to active releases
- BM-2071 - FIX: EventListeners on pipelines may not run after execution
- BM-2067 - FIX: Script assets should cause a validation error if spaces are added to the script name
To learn more about how we distinguish between major, minor, and maintenance releases, make sure to check out KB#1059 - When should I update?