QTest Deployment History API vs Jenkins Console Output Retrieval

Integration Between QTest Deployment History API and Jenkins

When a Jenkins‑triggered deployment fails, the QTest Deployment History UI offers a compressed log download link, but the REST API only returns a temporary URL. The URL typically expires within 15 minutes, and the API does not provide the raw log content directly. This gap makes automated log collection difficult, especially when downstream pipelines need the log data for diagnostics or compliance.

The uncertainty lies in whether the API can be configured to return the log payload itself, extend the URL’s validity, or capture Jenkins console output automatically without manual intervention.

Given these constraints, we need to determine the best approach to reliably retrieve complete logs for failed deployments.

• What configuration or API enhancement is required to return raw log content instead of a transient URL?
• Is there an option to increase the expiration window for the log URL or to pre‑fetch the log before it expires?
• How can Jenkins be set up to automatically forward its console output to QTest so that the Deployment History captures it without additional steps?