Buildforge 8.0.0.1 - Max Threads cannot be changed after project has been run
3 answers
Hey Dennis.
Nope, no trick. This looks like a defect. I would open a PMR and notify support so that they can go through the process. If this is crucial functionality there is always a way to change it within the database, but i will let support guide you through what may be necessary.
Thanks!
It seems IBM has disabled the "Max Threads" in Buildforge 8.
https://jazz.net/downloads/rational-build-forge/releases/8.0?p=releasenotes
"The Java MJC Project property "Max Threads" does not work because the value of the Max Threads property is deprecated in MJC. Due to limited resources used for parallel step processing in MJC, the "Max Threads" limitation has little value for MJC execution."
I think this seriously devalues the tool. The 200 parallel builds will just all get dumped on the servers in one whack instead of the old-fashioned thread limiting to 20 or 30 concurrent builds...
https://jazz.net/downloads/rational-build-forge/releases/8.0?p=releasenotes
"The Java MJC Project property "Max Threads" does not work because the value of the Max Threads property is deprecated in MJC. Due to limited resources used for parallel step processing in MJC, the "Max Threads" limitation has little value for MJC execution."
I think this seriously devalues the tool. The 200 parallel builds will just all get dumped on the servers in one whack instead of the old-fashioned thread limiting to 20 or 30 concurrent builds...