Skip to content

Conversation

@reshmifrog
Copy link
Contributor

@reshmifrog reshmifrog commented Sep 26, 2025

  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • All static analysis checks passed.
  • Appropriate label is added to auto generate release notes.
  • I used gofmt for formatting the code before submitting the pull request.
  • PR description is clear and concise, and it includes the proposed solution/fix.

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 using jf 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.

@reshmifrog reshmifrog added the bug Something isn't working label Sep 26, 2025
@reshmifrog reshmifrog changed the title add timestamp as props for python add timestamp as props for twine Sep 29, 2025
@reshmifrog reshmifrog added the safe to test Approve running integration tests on a pull request label Sep 29, 2025
@reshmifrog reshmifrog merged commit d9c7efa into jfrog:main Sep 30, 2025
11 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working safe to test Approve running integration tests on a pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants