versionfrom the redis plugin POM?
SaveableListener). I found https://stackoverflow.com/questions/4317035/how-to-convert-inputstream-to-virtual-file which suggests basically creating a temp file on disk. One interesting answer is https://stackoverflow.com/a/17595282/8461040 (first comment on this) which suggests using an Apache Commons VFS RAM file as a way to have an in memory file. But it seems like it cannot be converted to a
java.io.Fileas mentioned here : https://stackoverflow.com/questions/58140765/use-apache-commons-vfs-ram-file-to-avoid-using-file-system-with-api-requiring-a
Subject: Ideas Discussion: Tracing fingerprints (artifacts, credentials, docker images, etc.) across Jenkins Instances!
I would like to start this thread to discuss some opinions and new ideas with the community regarding fingerprints and tracing.
We have been working on the Jenkins link:[fingerprint] engine, and we have made great progress so far. We have been able to make the Jenkins fingerprinting engine 'pluggable', which basically means that now the fingerprints created by Jenkins can be stored in the cloud, away from the local disk storage of Jenkins master. Currently we only have one link:[plugin] which can support this, which is powered by Redis.
One of the advantages we got out of this project was the ability to track fingerprints across instances. What this can help in achieving is tracking usage of artifacts, credentials, docker images, etc. across instances of Jenkins. We can leverage our current project to provide such functionalities. But doing so only makes sense if there is some need for it. Also, there can be other potential use cases that we may have missed. We would love to discuss ideas around this, which can benefit the Jenkins community.
More information about the project can be found on the link:[project page] and link:[blog].
We would deeply appreciate suggestions and comments on this topic from the developer community, and potential areas where you think this project can help you or other Jenkins users.