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
Is your feature request related to a problem? Please describe.
I use an Artifactory repository for artifacts that are staged on a Linux machine. The Artifactory repository represents the 'publicly available' version, for internal use. Upon release, the artifacts are upload to the repository. Generally, there are few changes but 'jfrog rt upload' will always report all files during the upload. It's difficult to see which changes are being applied to the sync'd repository.
Describe the solution you'd like to see
Somewhat like the AWS CLI 'aws s3 sync' command works, I would like to see an an analogy for the JFrog CLI 'jf rt upload'. Most specifically, I'm interested in the reporting of new/modified/deleted files during the upload. I'm far less concerned about the actual actions under-the-hood
Describe alternatives you've considered
Nothing really, just leaving it as it is. It's mildly inconvenient but not worth much fuss.
Additional context
See support ticket 335243 for additional details.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I use an Artifactory repository for artifacts that are staged on a Linux machine. The Artifactory repository represents the 'publicly available' version, for internal use. Upon release, the artifacts are upload to the repository. Generally, there are few changes but 'jfrog rt upload' will always report all files during the upload. It's difficult to see which changes are being applied to the sync'd repository.
Describe the solution you'd like to see
Somewhat like the AWS CLI 'aws s3 sync' command works, I would like to see an an analogy for the JFrog CLI 'jf rt upload'. Most specifically, I'm interested in the reporting of new/modified/deleted files during the upload. I'm far less concerned about the actual actions under-the-hood
Describe alternatives you've considered
Nothing really, just leaving it as it is. It's mildly inconvenient but not worth much fuss.
Additional context
See support ticket 335243 for additional details.
The text was updated successfully, but these errors were encountered: