This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Run concurrent Builds with IS automation interface on a TFS build server
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 10, 2014
08:59 AM
Run concurrent Builds with IS automation interface on a TFS build server
I use a tool written in C# which manages the build of my Install Shield Projects by using IS 2012 the automation interface. The tool checks aut the ISM-projects, increases the version number , builds, checks in and so on.
Now I am using a TFS build server with different build agents. Is it possible to use the tool to build concurrent setups on the different build agents? This would speed up the build process, because the setup build time is the factor which determines the overall build time.
In the past I often had locks when trying to build concurrent setups on the same machine.
Has anybody experiences in doing this?
Best regards
Barbara
Now I am using a TFS build server with different build agents. Is it possible to use the tool to build concurrent setups on the different build agents? This would speed up the build process, because the setup build time is the factor which determines the overall build time.
In the past I often had locks when trying to build concurrent setups on the same machine.
Has anybody experiences in doing this?
Best regards
Barbara
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 23, 2014
10:40 PM
Each build agent would have its own installation of IS standalone so their would be no issues with locks. You would just need to add some sort of queuing functionality to your application and send separate build commands to the individual agents. You will also want to start each build task in a separate thread so that you can individually monitor them for completion.