Page Comparison

Workflow Execution Threads

Provides the customer with the ability manage the thread pool size for workflow executions.

Since @Since 6.5.0.13

• Workflow Execution Threads setting can now be updated without needing restart of FlexDeploy server.

• New system setting Project Execution Limits is now added to limit max number of concurrent workflow executions by Project. This can be useful if specific project deploys to many targets. This would allow other projects to continue execution and not exhaust all available threads in pool.

• Workflow Executions on higher sort number environments (like Production) If workflow execution threads are exhausted, pending executions for environments higher in sort order will be considered first for execution when threads become available, i.e. preference will be given to environment at the bottom on environments list. See Environments to understand about environment sort order.

20

Project Execution Limits

available since @Since 6.5.0.13 - see Workflow Execution Threads description above.

Configure this by adding individual lines for projects that you want to configure for execution limits. Each line must have two values separated by = sign. Put project id on left side of equal and add max concurrent executions per project limit on right side. See example below where project with id 122830 will be allowed max of 2 concurrent workflow executions whereas 230343 project will be allowed maximum of 5 concurrent workflow executions.

122830=2
230343=5

Plugin Execution Threads

Provides the customer with the ability to manage the thread pool size for plugin executions.

20

Continuous Integration Threads

Provides the customer with the ability to manage the thread pool size for continuous integration executions.

5

Release Automation Threads

Provides the customer with the ability to manage the thread pool size for release automation executions.

20

SSH Keep Alive Interval

Sends keep alive message on SSH sessions to prevent firewalls from terminating idle connections. Set to 0 to disable Keep Alive for SSH connections.

240 (seconds)

SSH Timeout

Timeout setting in seconds for SSH connections to Endpoints during workflow execution. This value defaults to 0 which means no timeout.

If you decide to set this value, it should be smaller than Keep Alive Interval (i.e. both keep alive and timeout should be adjusted appropriately)

0

SSH Connect Timeout

Timeout setting in seconds to establish SSH connection. This value defaults to 10 seconds.

FlexDeploy will do 3 retries for connect if not successful, with 1 second delay between each attempt.

10