Thanks Ben. JNDI was already planned for version 0.1 but didn't make it. I'll add it at some point for sure. I am not sure I understand the concept behind the build_stats but you're more than welcome to contribute if you wish. I would only ask please to add all these good ideas to the GitHub site as enhancements, so we don't lose track of them and we can plan the features roadmap. Thanks. M.
On Thursday, October 11, 2012 10:38:54 AM UTC+11, Ben Castellucci wrote: > > Ima hijack this real quick just to throw in a few comments unrelated to > what is actually being requested... > > First this looks like a really cool plugin. Nice job! I want to use this > but first... > > It may be advantageous to offer a configuration option of using a > datasource via JNDI defined at the container level. Even Jenkins' built-in > Winstone servlet container suports JDBC connection pooling with JNDI > lookup. Also, many Jenkins deployments reside in containers such as > Weblogic that offer strong credential encryption. The advantages to using a > connection pool versus building up and tearing down a connection each time > are obvious. > > Also, it would be extremely flexible if the schema offered a build_stats > table that was 'verticle' instead of 'horizontal' meaning there are just > generic 'id', 'name' and 'value' colums for the stats. Each row could be a > different stat, it's id tied to a row in the build_details table. This > could allow dynamic stats, configurable either at the Jenkins level or the > job level (think checkbox list of availabe stats to audit). The available > stats could be added to over time and existing schemas would still be valid. > > And... it may be more helpful if the build_stats table had actual job > name, build # and build id instead of build number as the name. > > I may be interested in contributing but time is tight... > > Let me know any thoughts. > > Thanks! > Ben > On Oct 10, 2012 7:44 AM, "Marco Scata" <msc...@hotmail.com <javascript:>> > wrote: > >> Hi all. >> >> I'd like to have my new plugin on Jenkins org if possible. >> Current source is on GitHub >> https://github.com/mscata/jenkins-audit2db-plugin.git >> My GitHub ID is mscata >> >> Can I also use the Jenkins CI infrastructure? At the moment it's using >> CloudBees. >> >> I also started writing a wiki page at >> https://wiki.jenkins-ci.org/display/JENKINS/Audit+To+Database+Plugin >> Hope that's ok. >> >> Marco >> >
