You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When uploading result to Depency track (using projectName and projectVersion each time with different version and with synchronous result) the ProjektId is overridden.
After the upload the Project id is now pinned to that Project so new version are ignored.
Environment
Plugin Version: 4.1.1
To Reproduce
Steps to reproduce the behavior:
Configure Plugin with projectName and projectVersion (ignore ProjectId)
Upload first version (now the Project id should be configured)
Upload second version
Result is published to the first Project
Expected behavior
Plugging configured with projectName and projectVersion should keep this setting and not use the projectId in further request.
If you would like to continue using the sync mode for different projects (names and/or versions) in one build job although it does not make any sense, you can set projectId to an empty string upon each invocation.
My use-case is one job for a project with different branches (versions). And it is not an option to update the job manually after each invocation.
If this this it not supported than it should not be possible to save this setting via UI in the plugging. This is what not make sense to me. If a save some setting the setting (with just name, version and projectId as empty string) this setting should persist. But after a build the projectId is overridden. Easy fix for that would be not set the projectId globally in this class.
I now understand what you actually mean and where the problem lies. I will take care of it. By the way, the information about Jenkins version and job type, which you have withheld so far, is requested at the beginning with good reason.
Describe the bug
When uploading result to Depency track (using projectName and projectVersion each time with different version and with synchronous result) the ProjektId is overridden.
After the upload the Project id is now pinned to that Project so new version are ignored.
Environment
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Plugging configured with projectName and projectVersion should keep this setting and not use the projectId in further request.
Additional context
i think this is the broken part:
projectId = apiClient.lookupProject(effectiveProjectName, effectiveProjectVersion).getUuid();
The text was updated successfully, but these errors were encountered: