210 - Deployment Delights

In the last sprint cycle, we focused on improving several aspects related to the deployments. It is now possible to see an overview of container versions, and containers will not be deployed and restarted when no changes have been made. Moreover, several bug fixes have been done relating to the Flow Designer, the Deploy phase, and alerting.

Please find out more on our Release blog.

New features

• Deploy - Releases: We added the possibility to see the container versions in the release details. This can be viewed by clicking the three dots of the release in the Deploy phase.

Minor changes

• Deploy - Releases: When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
• Deploy - Containers: Changing the list of flows that should run on a container will now trigger the rebuilding of images.

Bug fixes

• Create - Flow Designer: An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
• Create - Flow Designer: We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior. (#1100)
• Deploy - Containers: The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
• Deploy - Deployment plan: We solved a bug where a deployment step in the deployment plan could randomly get stuck.
• Deploy - Runtimes: We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
• Manage - Alerting: The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
• Manage - Alerting: We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.