What limits the number of concurrent builds?

Continua CI Discussion
1

I am only using one agent on the main build server, and we have an extra five-pack of concurrent build licenses - but still the number of concurrent builds never exceeds two.

Is it bound to the number of physical cores?

The server is VM on Azure
Processor Intel® Xeon® Platinum 8171M CPU @ 2.60GHz, 2095 Mhz, 2 Core(s), 4 Logical Processor(s)
and it is insistant on running only two concurrent builds.

The old server was a VM on a regular server.
Processor Intel® Xeon® CPU E5-2643 v4 @ 3.40GHz, 3392 Mhz, 4 Core(s), 4 Logical Processor(s)
and it happily ran six concurrent builds.

Why the change in behaviour?

image
image1507×758 68.6 KB

2

It’s a default setting per agent (2) - on the admin Agents page, there is a Concurrent Stages column, you can change that setting per agent.

1 Like
3

Thanks, Vincent!
I have a lot to learn about Continua CI, for sure.
But I LOVE it!

2 Likes
4

It does make me wonder, though - why wasn’t the quantity of concurrent builds reflected through the restore? Is it stored in the registry?

5

Did your agent names change? If so that would be why.

6

TBH, I don’t know. I did not change the default agent name in the new installation, and I didn’t change the name after the drop/restore, but I cannot say for sure that it hadn’t changed from the old machine.

I did remove a second agent which we no longer used - but that was for a second server that we had since long stopped using.