Jenkins is the authoritative source of whether a Git commit SHA1 has passed 
or failed to build. How do I, several weeks after the build is done, 
interrogate Jenkins about a specific Git commit SHA1? Seems to me I have to 
scan a hole bunch of XML files until I find the right one. Does not feel 
like a fast lookup to me, more like a slow walk of all the XML files (O(N) 
rather than O(1)).

Is the Audit to Database plugin a good idea to solve this?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fb2812d0-2c9d-4acb-ac2f-c917ccc1ebf7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to