After upgrading Jenkins to version 2.580, the qTest Jenkins plugin version 2025.1 fails during test result submission with the following error:

 

{{java.lang.ClassNotFoundException: org.apache.commons.lang.StringUtils
Caused: java.lang.NoClassDefFoundError: org/apache/commons/lang/StringUtils}}

The failure occurs in the qTest plugin during execution of:

 

com.qasymphony.ci.plugin.action.SubmitJUnitStep$SubmitJUnitStepExecution.run

Jenkins removed Apache Commons Lang 2.x from Jenkins core starting with version 2.579. The qTest 2025.1 plugin still references org.apache.commons.lang.StringUtils, which belongs to Commons Lang 2.x, but the plugin does not appear to declare the required Commons Lang compatibility dependency.

As a result, Jenkins 2.580 can no longer load the required StringUtils class when the qTest Pipeline step executes.

Environment

• Jenkins version: 2.580
• qTest Jenkins plugin version: 2025.1

Impact
Jenkins pipelines that use the qTest plugin to submit JUnit/test execution results fail during the qTest submission step. This prevents automated test results from being published to qTest and causes affected pipelines to fail.

Expected Behavior
The qTest plugin should successfully submit JUnit/test results when running on Jenkins 2.580.

Actual Behavior
The qTest step fails with ClassNotFoundException / NoClassDefFoundError for:

 

org.apache.commons.lang.StringUtils

Likely Root Cause
Jenkins 2.579+ no longer bundles Apache Commons Lang 2.x in Jenkins core. qTest plugin 2025.1 still depends on the Commons Lang 2.x StringUtils class without declaring the appropriate Jenkins commons-lang-api plugin dependency.

Recommended Resolution

• Check with Tricentis/qTest for a plugin release that supports Jenkins 2.579+.
• If no compatible release is available, evaluate patching/rebuilding the qTest plugin to explicitly declare the Jenkins commons-lang-api dependency.
• As a temporary workaround, evaluate rolling Jenkins back to a pre-2.579 version until a compatible qTest plugin is available.

Acceptance Criteria

• qTest test result submission completes successfully on Jenkins 2.580.
• Jenkins pipelines using the qTest SubmitJUnitStep no longer fail with ClassNotFoundException or NoClassDefFoundError.
• The implemented solution is validated in a non-production Jenkins environment before production deployment.
• The final resolution does not require manually placing dependency JAR files into Jenkins core/library directories.