Hi,
the downside of using a ephemeral lock like "${NODE_NAME}-display" is that you
cannot select a node where the resource is actually free.
In the worst case, all your builds that require a display are using the same
node,
blocking each other while other nodes are still free. This is not a probl
On 2023-05-28T11:54:43 +0200
opayq...@chsc.de wrote:
> Hi,
>
> have you considered naming the resource "${NODE_NAME}-display"?
>
> AFAIK you dont need to create them beforehand, lockable resources plugin
> creates missing resources automatically (temporarily).
I didn't know either of those two
Hi,
have you considered naming the resource "${NODE_NAME}-display"?
AFAIK you dont need to create them beforehand, lockable resources plugin
creates missing resources automatically (temporarily).
BR
On 28 May 2023 11:33:10 CEST, "list+io.jenkins.users via Jenkins Users"
wrote:
>Hello!
>
>I h
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 di
