Open moshavnik opened 3 months ago
Do you need this on the build log ? Because I think most of it is available on Jenkins log if you enable TRACE/ALL logging for the io.jenkins.plugins.artifactory_artifacts
package. From what I remember you can see all API call done to artifact backend.
This plugin is quite new and right now I didn't do any "performance" test by uploading large artifact on Artifactory
The plugin is using internally a Java library from JFrog (https://github.com/jfrog/artifactory-client-java?tab=readme-ov-file#uploading-an-artifact) so I'm not sure if there is anything we can optimize there
I need it in the build log so the users using this feature will have a simple way of knowing this information. the place I work at has a lot (thousands) of pipelines. the more information the log has, the less time we spend looking for "what went wrong" in other places.
that's why this information is useful to us.
like I said, the default option can stay "clean log"...
What feature do you want to see added?
when the archive artifacts finish successfully, i would like to see a short informative summery of the process: how many artifacts were archived? how long did it take? what's the total space consumed by the artifacts? what's the average transfer rate speed?
anything else you think is useful.
Upstream changes
No response
Are you interested in contributing this feature?
No response