Skip to content
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

add archive summery to the console output/log. #16

Open
moshavnik opened this issue Mar 28, 2024 · 2 comments
Open

add archive summery to the console output/log. #16

moshavnik opened this issue Mar 28, 2024 · 2 comments
Labels
enhancement For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted

Comments

@moshavnik
Copy link

moshavnik commented Mar 28, 2024

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

@moshavnik moshavnik added the enhancement For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted label Mar 28, 2024
@jonesbusy
Copy link
Contributor

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

@moshavnik
Copy link
Author

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"...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted
Projects
None yet
Development

No branches or pull requests

2 participants