Unable to de-assign projects from agents

Attaching the image doesn't seem to have worked, so I'm trying again.

As you can see, the grey "X" at the right side (within the red borders) is missing for some projects. Why is that?

Hello!

The pools in question are also assigned to other pools, hence if you would remove them from Default pool they would still have a processing capacity attached to them. We do not allow to remove project from all pools intentionally to avoid case when project builds can never get an agent assigned.

I hope this helps; please let me know if there are any other questions.

Hi Fedor,

thank you, that helped indeed. In general I'm not really fond of the concept/idea of having non-removable default things with special behavior, but that is may just be my personal preference regarding software design.

I think I'll make the Default pool the "Unused Pool" where all the unused build configurations go.

1.)

Is it possible for the Default pool to have no agents attached?

Feature request: Please think about making the default pool re-nameable. That would allow me to put a proper label on it.

2.)

How can I move archived build configurations from one pool to the other? The only way I see is to un-archive, move and re-archive them. Archived build configurations don't show up in the "Assign projects" dialogue.

Feature request: Make them move-able just like normal ones.

3.)

It seems if you have a project assigned to a pool A, and all build configurations below that project assigned to another pool B, you find yourself unable to remove the project from pool A. But you can remove it from pool B, where it is not assigned to. What would happen if I press that X to remove it from there? Would it remove the build configurations underneath? That's unintuitive.

I'm not sure if I just didn't grasp the concept yet.

To be honest I don't see a reason adding projects to pools is allowed at all. Isn't the link implicitely given through the build configurations?

Feature suggestion: Display projects in this page for informational purposes only (to group the build configurations), but do not provide means to add or remove them.

In the following screenshots, each build agent is in a seperate pool. I forgot to include the pool headlines.

(I hope I don't come across harsh. I don't mean it this way. This is not my native language.)

Best regards,

Manuel

Hello Manuel!

Apologies for the delay; speaking of your questions:

1) yes, sure, Default pool may have no agents at all. Please mind that the Default pool name is largely linked to the fact that it is a default target for new agents; however, speaking of the pool rename feature, you could request one via https://youtrack.jetbrains.com/issues/TW.

2) am I correct to assume you have meant archived projects? Could you please confirm why an archived project would require a change of assigned pool? Just in case, agent pool view has a checkbox to hide the archived projects (so if the projects list is not easily traversed, perchance this would be helpful):


3) let`s say you have a project P which has a build configuration B; you also have two agent pools, P1 and P2, containing A1 and A2 agents respectively. A project may have several pools assigned which will mean its build configurations will use those pools for the agent selection. I have created a local setup where P has P1 assigned, but B has an agent requirement on A2 (which is part of P2 not assigned to P). As a result:
a) B would never start as there are no viable agents in its selection scope;
b) unfortunately, I could not reproduce a behavior where P2 is shown as assigned to P project. Could you please confirm the TeamCity version? (and external plugins if any are in use)