Hi,
I'm wondering how to handle labview code distribution. My team is using teststand as verification tool. Our teststand sequences mainly call our internal labview library. This library is a bunch of VIs versioned with subversion. When the library reaches a good stability point, a tag is created. So we only use tags when writing a test sequence (never the trunk).
Here is an example which describes my problem :
- User A writes a test sequence for product Y with the latest tag of the library (revision 1000).
- In the meantime, User B adds a few VIs and improves some others, comits its changes and creates a new tag (revision 1001).
- User A sees that there is a new tag (revision 1001) and overwrites its local library with it. He then creates a test sequence for product Z which runs just fine with the revision 1001. However, he then tries to run the sequence for the product Y but it crashes as one of the VIs has been changed between revision 1000 and 1001.
This is what I would like to avoid. The only solution I see for now, is to define the revision at the beggining of the test sequence and have a function that will checkout this version of the library before executing the sequence.
Do you see any way of handling this differently ?
Thanks,
Alex