Hello! I have a few build nodes on physical machines. Each machine has a GPU/display. I have a large set of projects (100+). For each project, each commit is built on all nodes using a pipeline (so there's a stage for "build on Linux", "build on Windows", etc). Some projects require access to a display in order to run automated tests for UIs, but most don't. When a build _does_ require access to a display, it really needs to be the only build using that display at any given time so that tests running in multiple projects don't trample on each other.
It sounds like what I want is a lockable resource; when a project is configured to require a display, it should use a pipeline that locks a display resource and then gives it back at the end of the build. That way, two builds on the same node don't interfere with each other's UI tests, and that builds don't require access to a display can still execute concurrently on the node. The problem: It doesn't seem like lockable resources are associated with nodes. It's not really clear to me how I can declare that each node has exactly one lockable display resource, and how I can express in each pipeline "lock the display resource available on this node". Is there some way to do this? Are lockable resources actually what I need? Maybe there's some other plugin better suited to this. -- Mark Raynsford | https://www.io7m.com -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20230528093310.535e8312%40workstation01.int.arc7.info.
