add timestamp as props for twine #260
Merged
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.
Problem: When publishing artifacts to artifactory using the jf-cli, uploading Python packages to a PyPI repository via the
jf twine command, and other artifacts to a generic repository usingjf rt upload, all under the same build name and build number. The build.timestamp property was not applied to the artifacts uploaded to the PyPI repository, whereas it is correctly applied to artifacts in the generic repository.Solution: Added build.timestamp as one of props for python packages.