Skip to content

Conversation

@jlrigau
Copy link

@jlrigau jlrigau commented Oct 7, 2015

When using Jenkins in a cluster, it is useful to have visibility global to all the nodes in the cluster and not only per node.

This PR allows to indicate visibility scope on port allocator configuration by adding a "Global Visibility" checkbox.

Global Visibility

@jenkinsadmin
Copy link
Member

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@andresrc
Copy link

Hello,

My main concern with this PR is that we are "allocating" ports on nodes w/o checking its availability anywhere. I may have misunderstood the use case, or maybe it not in the scope of this plugin.

Please open a JIRA issue and/or a mailing list thread to elaborate.

Thanks.

@jlrigau
Copy link
Author

jlrigau commented Nov 24, 2015

@andresrc the goal of this PR is similar to #5 (comment)

@andresrc
Copy link

Thanks @jlrigau . My concern then is that this use case is somewhat out of the scope of this plugin and may be confusing for some users. A "global" scope, could also imply that I want to reserve a port or port range in every node in the system.

This "external cluster configuration" including ports and other possible configurations that may be needed may be worth its own plugin.

@jlrigau
Copy link
Author

jlrigau commented Nov 27, 2015

Hi @andresrc,

I understand your point of view concerning the scope of this plugin but today the port-allocator plugin already satisfies two goals:

  • Reserving a specific port or port range
  • Managing a pool definition.

The global scope is only related to the pool definition feature and for me it is very important to manage cluster-specific behaviour within each plugin instead of having to develop a new plugin.

Configuring Jenkins with a cluster through a cloud manager is becoming a common usage today and adapting plugins according to this usage seems to be the right strategy.

@andresrc
Copy link

Let's move this forward. Would be possible to have a different name that makes much more clear that no Jenkins node is involved?

Besides, the name of the port manager should use the same notation (now it's a "Global Pool" but a ClusterPortManager) and the help include a more detailed description of the implications of using the field.

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants