Thanks, we do have a valid reason for storing data in the db, we will create a build step with groovy plugin to specifically put some the data into the db
On Tue, Apr 9, 2013 at 6:38 PM, Les Mikesell <[email protected]> wrote: > On Tue, Apr 9, 2013 at 5:32 PM, Ipoo Doh <[email protected]> wrote: > > Problem: > > I want to store build metadata in a db, things like Job and its build > > history details like The build number, time it started, time it ended, > > whether it succeeded, where the artiifacts are stored, wheather it has > been > > promoted, its svn tag details, etc... Other tools like our automated > testing > > framework will feed off these data in the DB and run their tests and > update > > their corresponding table (which will be linked to the build history > table > > by foreign key) with the results. Please let me know how i can achieve > this > > in Jenkins. > > > > I don't think there is a way to do that - or a real need to. Just let > jenkins trigger the next steps for you or use the rest interface to > control and track the activity. > > -- > Les Mikesell > [email protected] > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
