Describe the bug
When configuring the extension with an on-prem Artifactory 7.x instance, the generated link in "Xray Build Scan Report" points to /artifactory/ui/builds/ which is an invalid path. It appears that this issue does not occur with Artifactory Cloud instances.
To Reproduce
Configure Azure DevOps with an on-prem Artifactory instance (tested on 7.9.2) which is connected on an on-prem Xray instance (tested on 3.18.2).
Create a build pipeline which deploys a build to Artifactory and triggers an Xray scan. I have used this pipeline.
When the build concludes, click the "Xray Build Scan Report" and observe the 401/404 error.
Expected behavior
The link should point to the valid path, which is /ui/builds/
Workaround
A temporary solution is using a specific rewrite rule in the reverse proxy. For example, when using NGINX in front of Artifactory, locate the following rule:
Describe the bug When configuring the extension with an on-prem Artifactory 7.x instance, the generated link in "Xray Build Scan Report" points to /artifactory/ui/builds/ which is an invalid path. It appears that this issue does not occur with Artifactory Cloud instances.
To Reproduce
Expected behavior The link should point to the valid path, which is /ui/builds/
Workaround A temporary solution is using a specific rewrite rule in the reverse proxy. For example, when using NGINX in front of Artifactory, locate the following rule:
And add this rule above it:
This will redirect requests from /artifactory/ui/builds/ to /ui/builds/ while maintaining the build path.
Versions