Semaphore is shared between Jobs when using a Pipeline library.

[Xyaren]

As the title says:
Using a semaphore in a pipeline libary that is imported in multiple projects is shared between jobs.
Is this intended ?
How can I prevent this ?

[gpolek]

Do we have any update in this topic? We are heavily using shared pipelines and this causes deadlocks in our jobs.

[Spacetown]

I've the same Problem. With this restriction isn't usable in a multibranch pipeline. I think this is because the pipeline is always executed on the master.

[Xyaren]

Which is fine if the job name and build number is part of the "key".

[Spacetown]

@Xyaren But there is no key option.

[Spacetown]

I've searched arround and didn't a semaphore implementation with named semaphores. I think the only solution for this is to implement a own semaphore with synchronized functions doing spinlock with a sleep or using a BlockingQueue.

[touting15]

I've been impacted by the same thing. I never had any issues using the plugin until I began using it in another job's pipeline code.

[touting15]

Have you found any jenkins/groovy friendly solutions @Spacetown ?

[Spacetown]

@touting15 No.

[jondhoor]

Has there been any solution or workaround yet? We would really like to use this feature in a multibranch pipeline.

[Spacetown]

Has there been any solution or workaround yet? We would really like to use this feature in a multibranch pipeline.

Not from my side.

[zhihaoy]

I don't follow. What's the exact symptom? Is the story saying that the pipeline code that createSemaphore in a Multi-Branch pipeline will cause a deadlock when acquiring?