This articles discusses whether or not the following are possible:
Setting up a machine as both an ElectricAccelerator agent and an CloudBees CD (CloudBees Flow) agent
Configuring a machine as an CloudBees CD (CloudBees Flow)server and an Electric Make (eMake) machine
To configure the following workflow, begin with a CloudBees CD (CloudBees Flow) agent that also has eMake installed on it:
[CMDR_SERVER] -> [CMDR_AGENT, EMAKE] -> [ACCEL_AGENTS]
Accelerator consists of three elements:
A Cluster Manager, which runs a web server
Accelerator host machines where agents run compiles using EFS
A build machine where eMake runs, which initiates jobs through the Cluster Manager
In this architecture, the CloudBees CD (CloudBees Flow) agent must be added to the third element, the build machine running eMake. Then, when a CloudBees CD (CloudBees Flow) step starts an Accelerator build, eMake is started by the CloudBees CD (CloudBees Flow) agent. eMake then contacts the Cluster Manager to distribute jobs to Accelerator agents. Your Accelerator job is now being built on those agents, even though CloudBees CD (CloudBees Flow) has no knowledge or control over the Accelerator agents.
CloudBees CD (CloudBees Flow) Server and Accelerator Cluster Manager coexisting on the same machine is not supported or tested by Electric Cloud. The tool chains for each product experience installation conflicts and the product upgrades will not work.
A CloudBees CD (CloudBees Flow) agent and an Accelerator agent are not normally on the same machine. If the machine is being used for both CloudBees CD (CloudBees Flow) and Accelerator work, each will have a negative effect on performance of the other.