fix(QTDI-2261): fix publication of dependency reports#1168
Open
fix(QTDI-2261): fix publication of dependency reports#1168
Conversation
Contributor
Author
|
Here is Jenkins job for testing the reporting https://jenkins-connectors.rnd-ci.cloud.talend.com/job/component-runtime/job/build/job/PR-1168/2/
|
Contributor
|
almost sure that we had similar ticket in the Jira already =) lgtm |
ozhelezniak-talend
approved these changes
Feb 20, 2026
Contributor
|
and to be honest, it's "chore", because we don't fix anything production related |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Requirements
Why this PR is needed?
The Jenkins build generates reports about dependencies through two maven plugins:
versions:dependency-updates-reportandversions:plugin-updates-report. Both generate report intarget/reports.The next step in Jenkins build tries to gather the reports in the
target/sitewhich is a mistake.What does this PR adds (design/code thoughts)?
Fix the path where the reports are located.