-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The source.copy(dest)-functionality should deploy artifacts with checksums #162
Comments
hello. can i take this one? |
@sousajf1 we'll appreciate it! :) Feel free to create PR and show a solution! |
#208 a try :) |
@allburov if artifact, that should be copied, doesn't have a checksum initially, then user gets warning that was mentioned from this test I assume that it is more like a user error. Initial artifact must have checksum calculated, before we copy. I think we will not implement this, any objections? |
Hi,
Unfortunately I can't check anymore if this is actually true, since one of the instance was retired. Anyhow, feel free to close the issue. |
@stmlange if instances are different, then completely different mechanism is utilized under the hood |
@stmlange |
Using
Leads to warnings in Artifactory that the client hasn't published a checksum value (e.g. similar to this https://stackoverflow.com/questions/40009688)
Instead of directly deploying it, one would need to download the file, generate the checksum and the deploy it back. E.g.
(untested)
The text was updated successfully, but these errors were encountered: