Skip to content

Release notes per monthly delivery

Find below the release notes of the Squash components for the support of the automated tests, organised by monthly delivery.
These release notes contain pointers toward the ticket tracking system. In case this one is not open to everyone, a 🔑 symbol is present.

Deprecation of Allure reports

Since the 2024-03 release, Squash Orchestrator can generate a HTML report giving a full overview of the tests of a workflow. This is the same as for Allure reports, but the Orchestrator ones are more versatile and will be further expandable in the future. As a result, we plan to deprecate the support of Allure reports:

  • Q4 2024, the Orchestrator will stop generating Allure reports by default. The generation will be reactivable via configuration.
  • Q3 2025, the support of Allure reports will be dropped. No Allure report will be creatable anymore.

2024-07

Limitation on the reports generated by the insightcollector

A timeout can happen when the insightcollector needs to deal with too much data (to generate the execution log and the HTML report). This can explain why the reports may be missing from Squash TM. The issue has been identified and a fix is planned.

2024-05

2024-03

2024-01

Removal of the image of the Squash Ultimate exclusive micro-services

The image of the Squash Ultimate exclusive micro-services does not exist anymore. These micro-services are now in the Squash Orchestrator image. Their launch is conditioned by the presence of a license file (containing an Ultimate license). The declaration of this license file is described here.

CPU requirements

As a reminder, the CPU requirements described here must be met.
However, due to the large number of problems reported by our users, these requirements will be lifted from 2024-03.

2023-12

CPU requirements

For Squash Orchestrator 4.8.0 and Squash AUTOM Premium exclusive micro-services 3.13.0, the Docker container must have a CPU with the following features: CX8, CMOV, FXSR, MMX, SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, POPCNT, LZCNT, AVX, AVX2, BMI1, BMI2, FMA.
Recent (less than 10 years old) server CPUs are supporting these features, but you may use a virtualisation mechanism that disables some of them.
In this case, you can check the features supported by the virtual CPU by running the lscpu command (inside the container). Given the fact that lscpu lists the CPU flags instead of the CPU features, which are slightly different, the listed flags should include: cx8, cmov, fxsr, mmx, sse, sse2, sse3, ssse3, sse4_1, sse4_2, popcnt, abm, avx, avx2, bmi1, bmi2, fma.
If some features are missing, you need to configure your hypervisor to allow them.

2023-10

2023-09

2023-07

2023-06

2023-05

2023-04

2023-03

2023-02

Coupled upgrades

  • When upgrading Squash Orchestrator to 4.0.0, the Jenkins Plugin must be upgraded to 2.1.0.
  • Upgrading Squash AUTOM Premium exclusive micro-services to 3.8.0 requires upgrading Squash Orchestrator to 4.0.0.

2022-12

2022-10

2022-09

2022-07

Modification of the configuration files of the providers

The configuration files of the providers have been modified: 

apiVersion: opentestfactory.org/v1alpha1
kind: ServiceConfig
is replaced by 
apiVersion: opentestfactory.org/v1beta1
kind: ProviderConfig
If you have modified a provider configuration file in order to declare a hook (as described in the OpenTestFactory documentation), you should now declared it in a separate file (see the same page) and keep the default configuration file which is delivered in the Docker image. You may nevertheless continue to use the modified provider configuration file that you use before, but, in this case, you need to modify the two lines indicated above.

2022-05

2022-04

2022-03

2022-02

2022-01

2021-12

2021-11

2021-10

2021-09

2021-07

1.1.0 (June 2021)

1.0.0 (April 2021)

1.0.0.alpha2 (March 2021)

1.0.0.alpha1 (February 2021)