Making a small change to an old project - How do I know what versions of Drivers and RIO etc was used for the last good build?

[AnthonV]

If I want to make a small change to a legacy project of years ago, I want to limit my risk by using the exact same versions of LabVIEW, NI-RIO etc.  So I check out the project from the repo, but I don't know how to check what versions were used when the last know good build was made.  I don't want to introduce issues by mass-recompiling to the latest version.

What is best practice in this case?  I could, before every repo commit, take a screenshot of MAX's software tree and save this in the project folder.

Any ideas?  

[GuenterMueller · Accepted solution]

Instead of creating a screenshot from MAX: MAX can create a report for you. You can take all of the expected info from it.

[JÞB]

The report is a great idea!  I store both a max technical report and a project.NCE (HW config export) with each of my projects for this exact reason.  Those files have sure come in handy!

Also- its a good idea to make an image of the target as accepted and archive it somewhere.  ESPECIALLY for PXI based systems from NI.  (When the customer comes back for a "duplicate" just send the image with the PO and the system arrives fully configured)

[AnthonV]

Great advice thanks guys!