Daklu Posted October 20, 2010 Report Share Posted October 20, 2010 When building large apps continuous integration helps ensure you're not breaking your executable when you check in new code. I've seen posts indicating some of the larger Labview shops do this. My question is how would I set up a system to automate the builds? Eventually I'd like a system that monitors the repository, automatically builds new code, and fires off blamemails when the build breaks. Do you have a dedicated build machine? If so, does it require its own Labview license? (I haven't seen anyone refer to a separate LV tool that just does builds, so I assume it does require its own license.) Are your builds automatically triggered when code is checked in or do you have to invoke it manually somehow? How would you set up a system to monitor your repository, and which scc system do you use? Are there any command line utilities for executing builds? Do you have to open a LV project and use scripting? Do your builds automatically run unit tests you have created? This is just an idea I've had floating around in my head for a while. I'm nowhere near close to implementing it, but I'd like to get some idea of what's possible and how much work it would take. Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.