Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

The June 2020 (1.24.0) release introduces a significant engine upgrade across all hubs, public variable update, R node whitelist information, bug fixes and security patching.

Engine Upgrade

  • Kitewheel upgraded the engine to Python 3, improving the overall performance by 81% improved the overall performance by redesigning the data flow between the API and the engine, and many modifications to the engine run time.

  • Kitewheel also upgraded to the latest version of Python 3

  • This has resulted in improvements of up to 81% reduction in execution time and up to 364% more in throughput at the same time

  • The upgrade saw the following improvements:

    • Reduced Network Latency

    • Streamlined graph execution

    • Improved sharing rate of information across processesImproved consumption on the job queueOptimized threads for instance type

    • Metrics emitted through threads – non-blocking to execution

    • Reduced size of Engine formatted graph

    • Connection management pooling Rabbit

    • Python Optimization flag

    • Lighter weight container identified - switched from Debian to AlpineDeployed using a lighter weight container

Public Variable Update

  • Scope of public Kitewheel now specified the use of public variable and best practices, and removed some anomalies in public variable behaviors

  • Public variables within a visual test are now independent of all other visual tests and deployed graphs

  • Persistent public variables scope is now guaranteed to be shared across all deployed graphs within an a project and environment - this means one running graph can update public variable that’s being used by other graphs in the same project

  • [Public variables will be available at all times to a running graph from a project and environmentInitial ] - need to think about this

  • The initial values of persistent public variables will not be set by a newly deployed graph if they have already been set by another graph that is currently deployed from that project and environmentJobs that have yet to execute due to a backup should still be able to access persistent public variable values despite no graphs from the environment and project currently running

    • Previously deploying a new graph in the same environment would override the existing public variable values

R Node Update

  • Kitewheel has automatically included a few whitelisted packages and functions for users to use

  • Any additional packages and functions that fall outside of the whitelist will need to be submitted to Kitewheel Support and reviewed by Kitewheel security team

...

  • KIT-4632: SSO SAML Issuer and ACS corrections for certain providers

  • KIT-2258: Transactions does do not necessarily load in VTS visual testing console

  • A number of security fixes were also included

...