Ideas Discussion: Tracing fingerprints (artifacts, credentials, docker images, etc.) across Jenkins Instances!

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Ideas Discussion: Tracing fingerprints (artifacts, credentials, docker images, etc.) across Jenkins Instances!

Sumit Sarin
Hi Everyone!

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 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 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 project page and 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.

Best Regards,
Sumit

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0f7c5550-e3d4-4262-92a0-4f5154389f37o%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: Ideas Discussion: Tracing fingerprints (artifacts, credentials, docker images, etc.) across Jenkins Instances!

Tim Jacomb
Hi

Great to see work being done on pluggable storage.

Personally I’ve never used the fingerprinting feature, but I assume / hope there’s people out there who are able to chime in.

Thanks
Tim

On Mon, 13 Jul 2020 at 15:21, Sumit Sarin <[hidden email]> wrote:
Hi Everyone!

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 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 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 project page and 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.

Best Regards,
Sumit

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0f7c5550-e3d4-4262-92a0-4f5154389f37o%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiceXG9-zhZ9BioLZSA_EH_9E4qC3E_ns-s_c65JvOeaiw%40mail.gmail.com.