title: How Jenkins stores build information
body: <h2>What's I'm trying to solve</h2>
  
  <p>I've a job on Jenkins to trigger a shell script, which generates an artifact and uploads to NFS. I would like to add a flow for QA to visit Jenkins to promote the build as a release build after the build is verified. At the moment, the test is not automated so the trigger of promotion is manual. What the promotion does is moving the artifact on NFS to a different location. I'm thinking to either use Ansible or shell script to archive this.</p>
  
  <h2>What's the problem</h2>
  
  <p>The problem is that when the promotion is triggered, I need to know the location of the build on NFS, SVN#, etc for each specific build# in this Jenkins job. I'm wondering if there's existing plugin or solutions for this.</p>
  
  <h2>What I have in mind</h2>
  
  <ol>
  <li>As part of the build steps, gather these info and write it to a flat file / relational DB so that the build #, Build Path, revision # and svn diff are stored in the DB. When the promotion is trigger, a script will read from DB and perform the promotion.</li>
  </ol>
  
  <p>I think reading and writing to a DB is doable, but seems a bit overkill to me. I'm just wondering if i'm missing something here. I'm curious if Jenkins has built-in plugins for similar use case.</p>
  
  <p>Thanks! </p>