title: Jenkins declarative pipeline: How to fingerprint a file without archiving it?
body: <p>I have a Jenkins declarative pipeline job that has the end result of creating some very large output files ( >  2 GB in size ).  <strong>I don't want to archive these files in Jenkins as artifacts.</strong></p>
  
  <p>However, I would like to fingerprint these large files so that I can associate them with other builds.</p>
  
  <p>How can I do this, preferably in the post action of the pipeline?</p>