Release 4.0.1

This release focuses on issues which have been discovered in BDeploy 4.0.0 production use.

Features

• Allow importing an instance export where the original product version is not available on the server.
• Allow updating to a new product version if the current product version is not available on the server.

Improvements

• Small error handling improvements in BHive
• Improve tooltips on various columns in the dashboard and process details.
• Clicking the current product version on the dashboard will now always bring up the "update product" panel, even if no update is available.
• Re-add the manual "refresh" button to the "update product" panel.
• Improve column sizing, icons, etc. in various tables.
• Avoid spurious reloads of data triggered by unrelated changes in other browser sessions (different instance group, different instance).
• Activities are no longer displayed in global scope. Cancelling activities requires at least write permissions on the current scope (e.g. instance group).
• Show the name of the managed server responsible for an instance on the instance dashboard and instance configuration pages.
• Show a warning message if there are recurring problems with the WebSocket connection, so users at least know that there is something wrong.
• Instance dashboard will switch to loading state when reloading data from the server, e.g. right after pressing "Install"/"Activate".

Fixes

• Fix port shift feature to properly update underlying parameter values.
• No longer show various actions to users with the wrong permissions (which failed when clicked).
• Fix instance group logo overflow in instance group overview table.
• Fix optional global parameters having the wrong value when added in parameter configuration.
• Fix guards eagerly checking permissions if no user is authenticated (leads to spurious error messages).
• Fix updating the UI when saving changes to an instance group before notifying attached managed masters of the update.
• Fix instance group create/edit dialogs accepting SVG images which is not currently supported.
• Fix instance configuration dialog to be disabled while saving changes, before redirecting to the instance dashboard.
• Fix icons sizes and coloring on actions in tables.
• Fix messed up history entry loading after triggering an asynchronous update on the server, i.e. by pressing install, if there are more than one hundred history entries.
• Fix a problem where leaving an instance group and quickly entering the same instance group again would loose the change subscriptions, basically detaching the UI from any changes performed on the server.

Release 4.0.0

This release focuses around a completely reworked UI, as well as fixes and features related to that. This release is technically compatible with older 3.6.x servers, and can be used as CENTRAL (4.0.x) with existing MANAGED (3.6.x) servers.

Features

• UI and UX rework. This changes nearly all of the UI. See the updated documentation on the Homepage for more details.
• Deep link support in the new UI. Nearly all locations in the Web UI can be shared via link, provided the target user has appropriate permissions.
• CLIENT permission added, which allows to provide users with only the permission to view client applications on an instance group, e.g. for download.
• Product update/validation moved to backend. This allows to use a similarly powerful product update mechanism from the Web UI and the CLI - as long as problems can be resolved automatically.
• Various places in the UI now provide bulk-manipulation capabilities, most notably the Instance Overview.
• Support uploading and editing files in the data directory.
• The general coloring and icon scheme has been adapted and optimized for contrast.
• Common search logic on all pages, which can be engaged using CTRL+F.
• Persistent synchronization on CENTRAL. It is now no longer required to synchronize whenever visiting an instance. Any synchronization - regardless of who and where performed it - will last for up to 15 minutes.

Improvements

• Improved WebSocket based change and activities notification. This affects remote activity display in when 4.x is used together with older servers.
• Faster and more reliable detection of communication and version mismatch issues with the backend.
• Update most third party libraries, most notable Angular 12 and Java 17 at the moment.
• Instance banners can only be set using predefined color schemes to assure sufficient contrast.
• Implement possibility to transfer products (CENTRAL <-> MANAGED) from the CLI.

Fixes

• Fix minor issues in PCU data regarding retries and back-off timings.
• Fix recursive resolving of variables in config files and/or cross-application.
• Preserve signatures on JDK binaries. Using jlink unfortunately cleared the signatures.
• Performance: no longer force sync of filesystem after each written object in the BHive. We trade a little consistency vs. a lot of performance. Since meta-data is still written sync, the combination allows us to detect and repair any resulting problems.
• Fix file-system level clashes on operations on different instances which would write the same files in e.g. a pool directory.
• Prevent names with leading or trailing whitespaces for various objects.
• Instances without installed version can now also be deleted if the configured product version has already been deleted.

Release 3.6.7

Features

• The client launcher now offers actions for manual repairing and pruning of the underlying storage.

Fixes

• Multiple smaller fixes related to instabilities in the client launcher related to cleanup.
• Downgrade Java to 11.0.11 due to a SIGSEGV on Linux when using 11.0.12.

Release 3.6.6

Fixes

• A critical issue has been fixed which caused out-of-order object transfers. This could - in case of an error - damage the target BHive with prune being the only available fix.

Release 3.6.5

Improvements

• Much improved progress reporting for the launcher.
• Support passing additional command line arguments to launched client applications.
• Performance improvements for network communication when pushing/fetching.
• Various UI improvements for the launcher browser.
• Improved retry handling in case of network issues.
• Launcher delegation will now copy the existing application to the side-by-side launcher, which yields a huge performance improvement if one of multiple in-use servers is updated.
• Files which are critical to BDeploys operation (mostly everything) is now written synchronously to avoid file content corruption. This might have a performance impact, but trades for much improved consistency.

Fixes

• Fix various inter-vm race conditions whith high frequency and throughput BHive operations.
• Fix issues with stale lock files in various places.

Release 3.6.4

Fixes

• Contains a fix for an issue which has the potential to repeatedly break product imports if the product contains a file with a specified content more than once.

Release 3.6.3

Features

• We are in continued preparation for a 4.0.0 release. Until then no features are planned.

Improvements

• Documentation has been improved in certain areas.
• Various small improvements suggested by sonarcloud.
• The BDeploy Gradle plugin now targets Java 8, as it should always have been.
• Read as little information as possible when scanning for instance manifests. This also fixes a few rare race conditions when deleting other things, like products.

Fixes

• Fix UTF-8 encoding issue with launcher on Windows systems.
• Fix an issue where fetching of large files failed due to a conversion error between int and long.
• Fix handling of stopCommand on product version change - we now always recalculate it from scratch to avoid multiple issues.

Release 3.6.2

Enables TLSv1.2 for the client installers (C# based, .NET 4.5)

ATTENTION

This release contains a issue that leads to broken installers when the BDeploy server is running on Windows.

Upgrading to 3.6.2 is possible but afterwards the following workaround needs to be applied:

• Terminate the running BDeploy instance
• Locate the bdeploy.bat file in the bin folder of the server installation
• Change the default JVM options to the following
  • set DEFAULT_JVM_OPTS="-Xms64m" "-Xmx1g" "-Dfile.encoding=UTF-8"
• Save changes and restart BDeploy

The already downloaded installers remain broken and need to be downloaded again.

Release 3.6.1

This release contains a critical fix for a potential race condition during cleanup (and prune). The issue has the potential to break an installation and prevent the server from starting. The potential race condition has been present since the beginning but the probability of hitting it has increased a lot with changes in the recent 3.6.0 release.

Release 3.6.0

Features

• Update third party libraries, which includes major versions of many of them, including the full move from javax (JavaEE 8) to jakarta (JakartaEE 9) packages. This has a major impact on existing BDeploy plugins - they will also need to move to jakarta imports.
• LDAP: Ability to test connectivity to a single server in its configuration.
• LDAP: Ability to "trace" the authentication of a single user.
• Launcher/Installer: Add an "Install Now" button to prevent the installer from beginning work immediately. This will help with various anti-malware software which detect immediate remote requests in scanned software.
• Launcher/Installer: Add option to not create shortcuts to installed applications.
• Launcher/Installer: Show to the user which server will be contacted, and where (local directory) software will be installed to.
• Monitoring data collection: In preparation for future UI improvements various monitoring data is now collected and stored.
• Disable TLS 1.0 and TLS 1.1 protocols, enable TLS 1.3 protocol usage on the server.

Improvements

• Overall documentation improvements to better reflect recent changes.
• Allow setting of an instance group logo from the CLI.
• No longer require the instance description on the CLI when creating an instance - aligned with Web UI.
• Overall improvements in the cleanup job and manual cleanup - additional logging as well as various fixes.
• Copied process configuration JSONs are now formatted.
• Show underlying error(s) when updating server certificate fails.
• Flatten internal trees when listing objects in the BHive. This will substantially lower the memory consumption in various cases, most notably when calculating product disc usage.
• The export of a manifest now retries moving the exported directory to its final name multiple times to avoid conflicts with malware protection software on Windows.

Fixes

• Fix issues with updating managed servers through a central server.
• Fix issues with the login CLI command.
• Fix UnsupportedOperationException on Java 8 VMs when using the public API.
• Make sure that all parallel file operations in the BHive are awaited even on failure before returning results.
• Fix an issue with the launcher not working when used on Chinese windows installations with products whos vendor string contains special characters.
• Fix an issue in the plugin manager which prevented it from continuing plugin loading after a plugin failed to load.
• Fix an issue when using a '/' character in a managed server name which made it impossible to open the managed server page after saving.