Project configuration requiring multiple agents at once

Hi,

I'm wondering if there's a better way to support the scenario where the build job requires the use of multiple agents at the same time.

All our work is done on cloud agents and so it's quite costly to keep the agents running when not in use. When a new job starts the test process requires a client to send data to the server, however both the clients and servers will fully saturate the machine.  As such they cannot be run on the same agent.

At the moment we got it to work by having a composite job that does

Start server job A,A finishes as soon as server is done starting up (and agent has a high timeout value)

Start client job B which depends on A so we get the IP of the machine.

Start management job C that depends on both A and B, use the rest call to kill agent A.

I initially wanted to use a detached built for A, but detach builds don't seem to keep A alive till you tell it the job is done.

Is there another approach I could take that's easier?

0
1 comment

Hi Tamar,

Have you already tried to use a detached build for A? As far as I know, when the build is detached, the agent should skip all the following steps of the build, but I would not expect that it would kill A.

It seems to me that the biggest constraint here is not being able to run jobs in the same machine. Perhaps using a better machine that would not get fully saturated when running the jobs on the same agent could be beneficial here? It might be worth a try and compare the costs.

Thanks,

Guilherme

0

Please sign in to leave a comment.