Installation

The Turbo Build Accelerator has a single installer designed to install its components on each machine that will participate within the Turbo build Cluster.

The Installer provides a choice to install on a machine :

• The Scheduler (just one instance within the Cluster)
• The Agent
• Both Agent and Scheduler (not recommended except for simple testing)

Choose components to install

The Installer provides the choice to create the necessary Windows Service(s) and Windows Firewall rules. Note: the Firewall rules (inbound and outbound) are restricted to 'Local Subnet'.

Choose to create Services and Firewall Rules

It is recommended to let the Installer create the Windows Services and Firewall Rules for a no-hassle installation. The option is intended for advanced installations.

The Installer will automatically check for any running instances of the Turbo Build Accelerator processes and confirm for it to exit them.

Confirmation for closing Turbo Build applications

At the final stage of the Installer, you have the option to :

• launch the installer for the Turbo Visual Studio Integration Extension for seamless builds with Turbo from Microsoft Visual Studio.
• launch the Turbo Monitor to enter settings
• view the README.txt

Final stages of installation

More details on the installer for the Turbo Visual Studio Integration Extension is available here.

The Installer will install by default to :

• the Program Files (x86) folder (e.g. C:\Program Files (x86)\Turbo).
• the ProgramData folder (e.g. C:\ProgramData\Turbo).

Installation within your organisation has minimal impact with no need to provision additional resources such as an external database.

Security

The Turbo Build Accelerator executables and the Installer executable (e.g. turbo-2.0.3.0-win32.exe) are digitally signed using a DigiCert OV Certificate.

The certificate is securely located on a DigiCert-provided hardware token (SafeNet 5110+ FIPS) adhering to security certification 'FIPS 140-2'.

This provides confidence that what you install has not been tampered with by a 3rd-party.

Automated 'Quiet' Mode

The Installer can be used in 'quiet' mode for easy automated deployment (e.g. by Terraform or Puppet).

Example automation :

rem Using optional environment variables to pass information to the Installer 
set TURBO_CONFIG_COMMON_VALUES=scheduler.ip_address=MACHINE001;logging.level=debug
set TURBO_CONFIG_AGENT_VALUES=number_of_build_slots=7
set TURBO_LICENSE_FILENAMEPATH=C:\Users\Administrator\turbo.lic

turbo-2.0.3.0-win32.exe /log=turbo-installer.log /silent /TYPE=agent

/TYPE can be :

• agent
• scheduler
• both

The environment variables TURBO_CONFIG_COMMON_VALUES, TURBO_CONFIG_AGENT_VALUES, TURBO_CONFIG_MONITOR_VALUES and TURBO_CONFIG_SCHEDULER_VALUES take a semicolon delimited list of xml config path=value.

The environment variable TURBO_LICENSE_FILENAMEPATH contains a path to the license file. This file will be copied by the Installer into the destination bin folder (e.g. C:\Program Files (x86)\Turbo\bin)