Wanted to expand and sort of answer the questions I asked here.
- One solution, which is probably the best solution, is to dynamically
add more A and B resources. If you can spin up new resources then you're
guaranteed to have online, not running nodes which Jenkins can then just
Hi,
I feel like this is certainly a situation someone has run into before but I
haven't been able to think up a non-trivial solution for my use case:
- Lets say I have two pipelines, P1 and P2, that do stuff and both need
the same two executors/slaves/nodes A and B
- P1 enters the queu
