Skip to content

Squash Orchestrator 4.5.0 Release Note

Introduction

Squash Orchestrator is a set of micro-services to perform automated test execution workflows described in a specific format.

This release note describes the changes of Squash Orchestrator version 4.5.0 compared to 4.4.0.

Squash Orchestrator 4.5.0 was released on July 28, 2023.

New features

  • Issue qualitygate #10 Complete the evaluation of the quality gate to take into account the Squash TM metadata
    When defining a quality gate, Squash TM data (importance, nature, type, UUID… of a test case; iteration/test suite; CUFs and datasets; … ) can be used to define the scope of the tests to be considered for a given rule. The quality gate page lists the whole usable data and its syntax.

  • Issue orchestrator #397 The retention period for workflows should be configurable
    It was possible, in previous versions of the orchestrator, to configure the duration of retention of the workflow information using the retention_period_minutes parameter. But this mechanism was sometimes too limited, for example for teams wanting to keep the information for one day except during the weekends where they wanted to extend the retention period up to three days.
    It is now possible to define retention policies, each one being defined by a scope, a retention period, and a weight. Weights are used when the total number of workflows is getting larger than the maximum number of storable workflows, in which case the oldest workflows having the smallest weight will be deleted. See the details in the OpenTestFactory documentation.

  • Issue python-toolkit #96 Allowing timestamp functions in expressions
    Some functions related to date/time management (year, month, day…) are now usable in workflow expressions. They are listed in the OpenTestFactory documentation.

  • Issue java-plugins #28 🔑 Misleading log message "Unknown test plan"
    Issue java-plugins #48 Useless log when successfully published a message
    Issue java-plugins #50 Add timestamps in notifications
    Logs have been further improved:

    • Some useless messages have been removed and some other ones have been downgraded from DEBUG to TRACE.
    • Some logs were missing timestamps, this has been fixed.

Bug fixes

  • Issue otf-all-in-one-images #36 Expected services name does not match the subscribed ones
    Issue micronaut-java-plugins #50 Interpreters subscribe with the same name as the providers
    The declaration of some service names was incorrect, resulting in opentf-ready not working in the previous 2023-06 delivery.

  • Issue python-toolkit #95 "File has changed" message is displayed when qualitygate definition file does not exist
    The logs were sometimes erroneously reporting that the quality gate definition file had been modified.

  • Issue qualitygate #13 Quality gate rules with no name are not handled correctly
    The quality gate evaluation was failing for rules with no name. When a rule is unnamed, a UUID is now used as its name.

  • Issue qualitygate #14 Qualitygate name or rule name duplicates are not handled
    A WARNING message is now logged in case of a duplicate quality gate name or rule name. This message is also reported by opentf-ctl get qualitygate and opentf-ctl describe qualitygate.

  • Issue qualitygate #15 Invalid scope and no test in scope give the same result
    An ERROR message is now logged in case of a quality gate rule having an invalid scope. Such rule is reported with the status INVALID_SCOPE by opentf-ctl get qualitygate.