title: How to store jenkins build output with artifacts?
body: <p>I have a Jenkins (which I'm new to) system that has a few constraints imposed on it:</p>
  
  <ul>
  <li>master/slave arrangement</li>
  <li>slave is Windows 7</li>
  <li>installing plugins is likely to experience significant resistance</li>
  <li>builds are to be archived to a Windows share</li>
  </ul>
  
  <p>The goal is to have the output of the build <strong>and</strong> the log of the build archived to:</p>
  
  <pre><code>//server/share/archive/%BUILD_TAG%/
  </code></pre>
  
  <p>I'm using the post-build step <code>Send build artifacts to a windows share</code> to push the binaries to the archiving server, but I've yet to find a way to arrange for the build log to end up there too. I have discovered that the console output is available at <a href="http://jenkins/job/" rel="noreferrer">http://jenkins/job/</a>$jobTitle/$buildNumber/consoleText, but I'm not sure how useful that is going to be - I can't cause anything to run on the archive server to run. I'd like to maintain the separation that the master Jenkins knows about the slave and the archive, but the slave and archive are unaware of each other (that's assuming the <code>Send build artifacts...</code> step is running on the master rather than being pushed down to the slave to action).</p>
  
  <p>Another approach I explored was to have Jenkins store the artifacts locally (via <code>Archive the artifacts</code>), but then I don't see a way to promtply push the result + log to the external server.</p>
  
  <p>It seems that Jenkins is very flexible and that this scenario is likely already catered for, but I've yet to find out how.</p>