Skip to content

Squash Orchestrator 4.2.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.2.0 compared to 4.1.0.

Squash Orchestrator 4.2.0 was released on April 25, 2023.

New features

  • Issue orchestrator #268 Preserve JUnit console logs
    In order to facilitate the analysis of JUnit problems, a junit-run-log.txt log file containing the whole output of the mvncommand is now added among the test reports (so it is also transferred in Squash TM).

  • Issue orchestrator #342 Allow for dynamic pool changes
    Issue python-toolkit #71 Allow for dynamic hooks/pools changes
    When the definitions of hooks or pools are updated, it is no more necessary to restart the orchestrator, this one will detect the update and will automatically apply the new configuration.

  • Issue python-toolkit #78 Improve handling of incorrect external hooks definitions
    In order to detect more easily incorrect hook definitions, an error message will be logged every time the function, on which the hook applies, will be executed.

  • Issue orchestrator #348 Show used environment variables on startup
    The orchestrator logs now contain the dump of all the environment variables used by the SSH channel plugin.

  • Issue orchestrator #333 Allow for filters in observer endpoints that return collections of items
    The /channels and /workflows endpoints now support filtering: a selector can be added as a query parameter.

  • Issue orchestrator #300 Do not stop a workflow containing several unit tests if one is missing in the Git repository
    If a test plan refers a JUnit test which does not exist in the Git repository, the workflow used to be stopped when the orchestrator failed to execute this test and the following tests in the iteration/test suite were not executed. Now, the orchestrator will report the missing JUnit test as Blocked and the following tests will be executed.

  • Issue orchestrator #340 Handles empty targets and empty pools
    The orchestrator now supports empty targets and empty pools.

Bug fixes

  • Issue python-toolkit #74 Disable input normalization when inputs declares a pattern
    In the Squash Orchestrator 4.0.0 release, input parameters have been normalized to consider the _and - characters to be the same, but this should not have been done for patterns (e.g. for the patterns defining the files to attach using the actions/prepare-inception@v1 action). This has been fixed.

  • Issue orchestrator #253 JUnit/Cucumber execute : error message if the target folder already exists on Windows
    Some spurious error messages were reported when executing JUnit and Cucumber tests (due to the fact that when several tests are run, the targetdirectory created by the first executed test was improperly handled by the following tests). These messages are not present anymore.

  • Issue orchestrator #344 Check for invalid tags when using SSHCHANNEL_TAGS/SSH_CHANNEL_TAGS
    Issue python-toolkit #75 Special chars are not supported in the agent registration command although they can be used in ssh
    Special characters are not allowed anymore in the tags of a ssh channel.

  • Issue orchestrator #331 The agent channel plugin does not force an os tag
    Trying to register an agent, by using the /agents endpoint, with no OS tag will now be rejected.