Fix poetry publish bug in traditional flow #304
Merged
+4
−47
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.
Fix poetry publish artifact upload regression
Problem
jf poetry publishwith build-info-collection flags skips artifact upload in traditional flow.Root Cause: FlexPack code was incorrectly added to traditional flow in
poetry.go, causing early return beforepoetry publishcommand execution.Solution
Remove FlexPack from
publish()function in traditional flow. FlexPack should only run in native flow (JFROG_RUN_NATIVE=true).Changes
saveFlexPackBuildInfo()function (unused)