210 - Deployment Delights

Last modified by Carlijn Kokkeler on 2024/04/18 13:08

release-blog-intro.png

Hi there, eMagiz developers! In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.

Alerts

Topic approaching max size alert
The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.

Missing metrics alert
We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.

Feedback Items

Improved release build process
When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.

Container version overview
Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.

release-blog-210-deployment-delights-container-overview.png

Improved deployment process
The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.

Rebuilding of images
Changing the list of flows that should run on a container will now trigger the rebuilding of images.

Bug Fixes

Runtime metrics processing
The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.

Deployment plan
We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.

View all store items
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.

Out of memory behavior
We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.

Max fetch size
In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.

Fancy Forum Answers

As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:

Key Takeaways

Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:

  • If you have questions surrounding our Program Increment Planning, please get in touch with productmanagement@emagiz.com
  • If you have feedback or ideas for us, talk to the Platypus
  • Please inform us of new additions to the store (productmanagement@emagiz.com) so we can all benefit from these.
  • Clear your browser cache (Ctrl + Shift + Del)
  • Check out the release notes here
  • Start thinking about how the license tracker can aid your development
  • Start thinking about major, minor, and patch
  • Upgrade to the latest build number
  • Keep making great integrations

Let's stay in touch and till next time!

Information

* Indicates a Beta feature. If you would like to get access to this beta feature, please contact productmanagement@emagiz.com

** Indicates a next-generation-architecture only feature.