| Agent Settings | |
| Enable as Helper | This checkbox determines whether the Agent will serve as a Helper Agent and will contribute its CPU resources to Incredibuild Environment in future builds.
Selected – the Agent will serve as a Helper Agent.
Cleared - the Agent will not serve as a Helper Agent. | Selected
By default, the Agent serves as a Helper machine. |
| Max Helper’s Cores To Be Used | The maximum number of cores on the Agent Helper machine that can be used for a build execution. | -1
The -1 value means that all the cores of this Agent machine will be used by the Coordinator for a task distribution. |
| Max Initiator’s Cores To Be Used | The maximum number of cores that can be used by the Agent when acting as the Initiator of a build. | -1
The -1 value means that all the cores of this Agent will be used for a build execution. |
| Max builds to preserve in DB | The maximum number of previous builds that can be stored in the database of the Build History. Once the number of builds in the database reaches this value, the oldest builds are deleted automatically.
Note: Builds that were excluded from the auto deletion procedure through the Toggle Auto Delete action, are not affected by this value, and will not be deleted even when this limit is reached. | 50 |
| Minimum local cores for build | The minimum number of available cores required to start a new build using the ib_console command.
Note: It is recommended not to change this value to less than 4. | 4 |
| Build Cache Service URL | When using shared Build Cache, the location of the Build Cache Service machine containing the shared cache. | |
| Local Build Cache Size | When using local Build Cache, the size of the Build Cache. | 100 GB. |
| Max ib_console Executions | The maximum number of builds, which run using the ib_console command, that are allowed to run concurrently.
Note: The actual number can be limited by the number of cores available on this Agent machine, and the value of the Minimum local cores for build. | 10 ib_console instances |
