Hi there.
Steps to reproduce : Sync Group - Async Group - 3 VSS Get Latest Versions
OR
Steps to reproduce : ASync Group - Async Group - 3 VSS Get Latest Versions
Problem : Get Latest Versions and always running Sync.
FB Version : 6.3.0.150
Thank you.
This is as intended. Some actions simply cannot have more than one instance running at a time, usually for environmental issues. In the case of VSS, to make the actions work as intended we have to modify the user’s vss ini file, and we revert it when the action is done. For that reason we restrict it to one vss action at a time. If we could get VSS to do what we need without modifying the ini file we would,we’ve been working with the VSS command line for 9+ years and we’re still finding new (to us at least)issues with it.
Thanks you for that clear reason. It does makes sense.
I am having the same issue right now.
Our application contains about 50 different modules. When I build everything I pull each module individually using particular label. Since I am trying to utilize most of my Server CPU power and speed up the process I run compilers in groups. It does in fact save time (from 45 minutes for whole process to 25 minutes).
Recently I've been running into similar issue as first post of this topic. As I understand FinalBuilder uses command line to access VSS instead of just using their API. With API there wouldn't be a problem of rewriting ini file.
Is there are way I can limit total number of VSS actions running at once? This would be the easiest solution. Basically queue the VSS action if one is running already.
Alex, we switched from using the API to the command line for a reason, the api was incredibly buggy and unreliable. Api calls would either fail for no particular reason, not fail but not actually do anything, or in many cases, work fine with one version of VSS and not with another (like work with 6.0a but not 6.0c). The command line is a whole lot more reliable.
VSS Actions are already “queued”, in that they aquire a lock on the ini file.
For some reason when I ran VSS actions in async I am getting errors like this:
Error getting User Ini file
Cannot open file "C:\PROJECTS\Components\[modulename]\users.txt". The system cannot find the file specified
This error happens in different places if I run my finalbuilder project several times. 1 out 10 runs no errors will come up. There is no users.txt file in any of the module folders. I am not sure how can I correct this error. I just switched my finalbuilder project to build all solutions in sync mode and it takes about 60 minutes, vs 30 minutes if I ran in 2-4 thread blocks.