On 30 July 2013 10:03, Gunnar Morling wrote:
> 2013/7/30 Sanne Grinovero
>>
>> Nice idea. I think that would be even better, but requires some code
>> adaptations in the project, and some use cases are complex: JGroups is
>> requiring multiple ports for different types of inbound/outbound
>> conn
2013/7/30 Sanne Grinovero
> Nice idea. I think that would be even better, but requires some code
> adaptations in the project, and some use cases are complex: JGroups is
> requiring multiple ports for different types of inbound/outbound
> connections (and UDP connectionless), that could get trick
Nice idea. I think that would be even better, but requires some code
adaptations in the project, and some use cases are complex: JGroups is
requiring multiple ports for different types of inbound/outbound
connections (and UDP connectionless), that could get tricky to get
right.
I'm not ruling out t
Could we alternatively avoid the conflict by using different ports for
different jobs (if that's the contended resource), e.g. by leveraging the
Jenkins port allocator plug-in [1]?
This plug-in selects unique port numbers and makes them available to a job
run as environment variable from where it
Hi all,
I am enabling the "resources lock exclusion" plugin: this allows to
specify - using a string - a resource that a specific build requires
for exclusive access, preventing parallel execution of multiple builds
using the same resource.
I'm enabling two resources specifically:
- JGROUPS
- JB
