
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
Task
|
| Affects Version/s: |
0.9.2,
1.0 RC1,
1.0 RC2,
1.0,
1.0.1,
1.1,
1.2,
1.1.1,
1.3,
1.2.1,
1.4,
1.4.1,
1.4.3,
1.4.2,
1.5.0 RC1,
1.4.4 RC1,
1.5.0 CTP,
1.4.4 RC2,
1.4.4,
1.4.4 SP1,
1.4.5
|
| Fix Version/s: |
1.5.0 RC1
|
|
|
It'd be helpful if the task could be set to run at a lower or higher process priority on the system.
We're using the server for more than CruiseControl and some of the builds bring the system to a stand-still, including processes like ASP.net. At times, one build causes other builds to time-out, checking modifications by CruiseControl slows down infinitely, etc.
Not sure if this feature would fix the problem however since NANT fires off it's tasks as separate processes. Haven't been able to try if the priority would carry over to these later spawned processes (which are the culprit in the end).
NANT may also need a priority setting on tasks.
|
|
Description
|
It'd be helpful if the task could be set to run at a lower or higher process priority on the system.
We're using the server for more than CruiseControl and some of the builds bring the system to a stand-still, including processes like ASP.net. At times, one build causes other builds to time-out, checking modifications by CruiseControl slows down infinitely, etc.
Not sure if this feature would fix the problem however since NANT fires off it's tasks as separate processes. Haven't been able to try if the priority would carry over to these later spawned processes (which are the culprit in the end).
NANT may also need a priority setting on tasks.
|
Show » |
| No work has yet been logged on this issue.
|
|