06-17-2014 08:04 AM
I have an automated build server (Jenkins) that uses the LabVIEW IDE to build my code every time I commit it into SVN.
This works well most of the time but every so often it gets stuck on start-up of LabVIEW because the recovery dialog pops up and waits for user input.
Is there a way this can be suppressed?
I was wondering if starting the automated build version with a separate INI file would solve this problem. Any ideas?
Heiko
06-17-2014 08:23 AM
06-17-2014 08:28 AM - edited 06-17-2014 08:30 AM
You can disable automatic recovery by disabling automatic periodic saving from Tools>>Options>>Enviornment. This may have undesireable side effects but it will also prevent any saved history data from existing so the recovery manager has nothing to ask the user about.
06-17-2014 08:36 AM
The problem is that I currently run the build server on the same machine that I develop the code on. This means the build server uses the same installation of LabVIEW as I use for development albeit a different instance.
So what I believe is happening is that I crash my development version and the build version picks up the files for recovery.
Probably the easiest thing would be migrate the server to a separate machine or VM and to turn off AutoSave.
06-17-2014 08:40 AM
@hfettig wrote:
The problem is that I currently run the build server on the same machine that I develop the code on. ....
Don't do that. Autorecovery might pop-up and make the process problematic
06-17-2014 09:20 AM
Like the reporter who asked the astronaut if he has a hard time communicating being all sealed up in a space suit - to which the astronaut replied, "I can't hear you, I'm all sealed up in this space suit..."
Mike...