When updated the qtest-plugin to version 2024.3 we got an error that the „secretKey“ parameter was not given. 

The old „submitJUnitTestResultsToqTest“ call only used the „apiKey“. No „secretKey“ was necessary, so updating to qtest-plugin version 2024.3 breaks all of our build jobs because there is no fallback option for backward compatibility with the new „secretKey“ parameter.

The Jenkins build script with the „submitJUnitTestResultsToqTest“ call is part of the version control Tag.

We can easily add this „secretKey“ parameter for future Jenkins build scripts.

However, we cannot modify already released old Tags.

We need a solution to update to qtest-plugin version 2024.3 or newer with backward compatibility to already released old Tags. Please provide a functionality for making the  „secretKey“ optional rather than mandatory.

The Jenkins Plugin 2024.3 Release Notes confirm the impression that the „secretKey“ should be optional:

To secure your qTest experience, we added a new App Secret Key that you can use when you connect your Jenkins plugin instance to qTest.