Release 3.4.0

Features

• The static BDeploy launcher binaries are now digitally signed (Windows).

Improvements

• Show a hint if a new product version has updated configuration files on product update.
• Proper display of array defaults in command line help.
• Improve fsck output on the command line to show if (and which) manifest is broken if the root tree is problematic.
• Update various third party dependencies.
• Pushing and fetching now (again) checks the consistency of the manifests pushed/fetched.
• In case of problems during export (writing to disc), report the problematic path in addition to the problematic object ID.

Fixes

• Various fixes for the launcher regarding race conditions and synchronization
• Various issues reported by sonarcloud fixed.
• Fix issue with server log reading in CENTRAL mode.
• Fix issue in the launcher where launching of applications on older BDeploy servers was no longer possible.
• Fix issue accessing software repositories through the Web UI if the user has no global read (or stronger) permission.

Release 3.3.1

Fixes

• Don't check path ownership on windows - it is just impossible to get this right for services.

Release 3.3.0

Features

• Software Repositories can now host Products in addition to external software.
• Products can be imported from Software Repositories into an Instance Group.
• Path ownership validation. BDeploy validates that the root directory belongs to the current user.
  • ATTENTION: This can break existing setups, especially Windows Services are often setup to run as System, not the user who set up the root directory (i.e. executed init).
• Merged the hostname and set-mode tools into a config tool which also allows changing the BDeploy server port.
• Password fields are now no longer editable by default. Editing must be enabled using a dedicated button next to them. This should finally shut down Browser auto-fill.
• BHives are now no longer created on the fly by the CLI if the directory pointed to is not a BHive already. The init command has been introduced to make this process explicit.
• Pooling of server applications can now be controlled via app-info.yaml. Each server application can decide which degree of pooling (global, instance, none) is applicable.
• Get rid of the term slave. All occurrences have been rephrased and refactored to use the term node instead.
• The master and slave commands have been combined into a start command. The old commands are still available as alias to the new start command.
• Server side logging has been reworked. The administration section now includes a log file browser/viewer along with an editor to edit the logging configuration online. Modified configuration is propagated to all nodes.
• The client launcher, when launched without any .bdeploy file, will now open up a launcher window which allows to chose which already installed application to launcher, uninstall applications, and even modify the launch arguments.

Improvements

• Update to Angular 11, update build tools, third party libraries, etc.
• Provide a "deployment information file" per instance as public API on each node.
• Variable expansion for instance information can now access the currently active instance version.
• The "port" features of BDeploy now recognize ports in parameters of type URL (newly added).
• Ports now show a "rating" in addition to the port state which is derived from the port and application state.
• Ports and their state can now also be queried via CLI.
• The process' start type is now shown in the CLI when querying processes of an instance.
• Various improvements in the underlying code will improve maintainability of the backend.
• Product disc usage information is now calculated asynchronously and in a manner which can be cancelled without producing exceptions. It is also cached for a short time.
• Improve error messages on the CLI by removing a useless layer of exception wrapping with no additional information.
• Install and uninstall on multiple nodes now runs in parallel instead of sequential.
• Users with read permissions are now also allowed to view endpoint settings.
• The file viewer (data files, process output, log files) has been changed from ACE to Monaco which gives a whole lot of new features and possibilities.
• Along with the Software Repository rework, the upload of new software (and now products as well) has been improved and simplified.
• It is now possible to set a default attribute for the attribute grouping on instance group and instance.
• Improve error handling in case of underlying 404 errors from the backend.
• Record (and display) changes to the instance banner, both on the banner as well as in the instance history.
• The CLI command to start an application on a node now understands the --join argument, to wait until the application terminates.

Fixes

• Fix various errors in attribute grouping and searching.
• Fix unintentional uppercasing of various texts in the UI.
• More fixes related to faulty activities and thread cleanup issues.
• Fix an issue where a problem during synchronization could render an instance group broken on managed servers.
• Fix an issue where an export/import cycle of an instance version could break the UI.
• Adding attributes to instance groups or instances no longer creates a new instance version.
• Fix handling of unsaved changes in various dialogs.
• Fix issues related to loading and updating an instance banner.
• Minor UI improvements in the instance history.
• Fix an issue with file locking. Concurrent launchers were able to run locked actions when they were not supposed to.
• Fix an issue where the client launcher would delete its own software manifests (this is a cosmetic issue, even though it sounds bad).
• Fix an issue in the PCU where a process could get stuck in a certain state, as events could overtake each other.
• Fix an issue where the order of client application cards created on dropping would be swapped sometimes.
• Fix an issue where applications could be dropped on the wrong node (in addition to the correct one).
• Fix validation and display issues in the parameter configuration dialog.
• Fix an issue where the "a newer product version is available" notification would asume a requirement for administrative permissions.
• With read permissions only, custom editors are no longer shown in the parameter configuration, as they require write permissions even to read their content.
• Fix an issue where neither Configure nor View would be available on a process configuration card.
• Fix issues in the PCU which arose when the application immediately terminated (before the startup logic was even finished).

Release 3.2.0

Features

• Allow deletion of instance versions for global administrators.
• Instance Group and Instance attributes. Define arbitrary attribues and group/filter by them.
• Custom per-product version sorting. Products can contribute a plugin which is used to perform product version sorting.
• View changes in an instance before saving.
• Add Gradle integration for BDeploy: https://plugins.gradle.org/plugin/io.bdeploy.gradle.plugin

Improvements

• More changed related to avoiding browsers to autofill passwords in the process and endpoint configuration dialogs.
• Banner improvements: sizing, font, wrapping, scrolling.
• Banner now reloads if it is changed in another browser session (locally/remotely).
• TEA integration allows to manually override the product version built.
• Various small improvements to Instance History.
• Prompt user if he tries to synchronize an instance with local modifications (which will be discarded).
• Prompt user on instance global actions (e.g. 'Stop all processes').
• Launcher installer: add option to install for all users.
• The FSCK operation (both CLI and Web UI) on BHives now flush all caches.

Fixes

• Fix wrong duration formatting in the CLI and UI.
• Avoid errors in the browser console if the launcher service is still loading.
• Fix errors in the browser when refreshing the BHive browser.
• Fix problems with the display of remote activities in some cases.
• Fix problems with left-over marker databases in BHives when problems occur during pushing/fetching.
• Fix LDAP administrative dialog to set server ID correctly.
• Fix broken page titles and a related error in the browser console.
• Fix empty splash screens if the launcher has no cached positioning information for launcher text and progress.
• Fix various conditions that could lead to stale lock files in the launcher home directory. Also detect and remove stale lock files.
• Properly unload plugins loaded from products in an instance group if this instance group is deleted.
• Fix various conditions which could lead to inconsistent state if the disc space runs out amidst certain operations.
• Properly handle broken plugins in products (e.g. if a file named 'plugin.jar' is not even a valid JAR file).
• Fix various issues with launcher directory determination and handling.
• Fix stdin attachment to processes requesting it.

Release 3.1.1

Fix some minor issues introduced with the CLI rework and the Instance History.

Release 3.1.0

Features

• Instance Banners: Leave messages attached to instances for colleagues.
• Complete CLI overhaul: Switchable output data formats, streamlining of commands, and much more.

Improvements

• By default, hide users with global permissions in permission dialogs.
• The Data Files Browser now remembers the page size when refreshing.
• Allow usage of template variables in the name of applications in templates.
• Add refresh buttons to port lists on nodes and applications.

Fixes

• Fix a lot of warnings and code smells.
• Fix occassional issues with the detection of the new push mechanism.
• Fix some bugs in the new Instance History features.
• Fix an error in the frontend related to custom parameters with the new Port features.

Release 3.0.0

Features

• Support for server and client port parameters. Improved editing capabilities, port shifting, server port availability checks, etc.
• A new implementation for fetch and push, which improves performance by roughly a factor of 4 - depending on the workload
• Implement Instance History. The Instance History will show configuration, deployment and runtime events for any instance on a filterable timeline.
• Introduce exit code handling for client side applications. This allows to implement application-specific update logic for clients.
• Custom editor plugins are available in readonly mode as well.
• Support for deletion of data files in the data file browser. Requires administrative priviledges on the instance group.
• Searching and filtering in application parameters.
• Support uploading arbitrary content to software repositories.
• Support for evaluation of exit codes for non-keepalive applications.

Improvements

• Improved layouts in various pages.
• Improved navigation throughout the application, especially in the BHive Browser
• Update third party dependencies where possible.
• Improve PCU related communication with managed servers and their minions - this reduces traffic to actual servers.
• Hightlight selected process in instance overview.
• More robust deserialization of certain values in YAML files.
• Improved version mismatch detection between central and managed servers. Improved user feedback in case of mismatches.
• Support instance filters in CLI.
• All client downloads now directly refer to the managed server with its own URI, no longer using the URI known on the central server.
• Support setting additional instance group information on the CLI.

Fixes

• Correct panel switching on instance change in the instance overview.
• Fix storage and calculation of managed server version information to properly display update hints.
• Various fixes in the client application launcher. Fixes installation of launcher updates, client updates, cleanup of existing installations, etc.

Release 2.5.2

Fixes:

• Fixed an issue that product upgrade fails when the new version contains an application defining a stop command
• Fixed and issue that changes in parameter order where not reflected when upgrading from a previous instance

Release 2.5.1

Features

• A new software repository permission dialog allows to pass write priviledges to users. Previously only administrators where allowed to upload third party software.

Improvements

• Update to Angular 10, update other third party dependencies.
• Improve product version information card layout and information. Now also shows which (installed) instance versions are using a certain product.
• Better logging in case an LDAP server configuration is wrong or not working.
• Better logging in case a parameter reference cannot be resolved during install of an application.
• No longer automatically clear the 'follow' switch in the output viewer of a process as soon as the process terminates. Otherwise some output may be missed.

Fixes

• Fix various issues with the Instance and Application Templates features introduced in 2.5.0.
• Fix spurious auto-uninstall markers on instance versions.
• Fix a issue which could leave the launcher home directory damaged.
• Fix an issue related to activity reporting in case plugins are loaded into the server.
• Fix an issue where multiple client applications from different instances would use the same persistent data directory.
• Fix an issue where copying an application and pasting it on a node with a different OS would not update the application to use this OS as well.
• Fix stop command output redirection to append to the application output instead of replacing/truncating it.
• Fix copy/paste support in file/output viewer terminal (CTRL+C, CTRL+V, ...).
• Fic a potential concurrency issue in activity reporting.

Release 2.5.0

Features

• Application Template support. In addition to Instance Templates, single applications may now provide templates as well.

Improvements

• Show the display name of an instance group in dialogs where possible.
• Improve progress (and result) visualization when applying Instance Templates.

Fixes

• Fix issues with concurrently using ProductManifestbuilder in build tool integration.
• Fix problems with very long version numbers.
• Fix a misleading/broken log message regarding the cleanup job schedule.
• Fix an issue where empty directories where left over after deleting configuration files.