Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-10267

Allow tunnel to master from swarm nodes

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • swarm-plugin
    • None
    • master: ubuntu
      swarm node: Mac OS X

      I'd like to use the swarm plugin (https://wiki.jenkins-ci.org/display/JENKINS/Swarm+Plugin).

      It works like a charm but I also use the sonar plugin (https://wiki.jenkins-ci.org/display/JENKINS/Sonar+plugin), which pushes the metrics data to 127.0.0.1:9001.

      Is there a way to tunnel through swarm to the master? Otherwise I have to open the ip/ports to the public, which is not so nice... any ideas?

          [JENKINS-10267] Allow tunnel to master from swarm nodes

          Christian Trabold created issue -
          Fabrice Bellingard made changes -
          Component/s Original: sonar [ 15523 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 140455 ] New: JNJira + In-Review [ 175282 ]

          Oleg Nenashev added a comment -

          KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Oleg Nenashev added a comment - KK does not maintain this plugin anymore. Moving to unassigned to set the expectation
          Oleg Nenashev made changes -
          Assignee Original: Kohsuke Kawaguchi [ kohsuke ]
          Basil Crow made changes -
          Affects Version/s Original: current [ 10162 ]
          Issue Type Original: Improvement [ 4 ] New: New Feature [ 2 ]
          Basil Crow made changes -
          Summary Original: Allow tunnel to master from "swarm" nodes New: Allow tunnel to master from swarm nodes
          Basil Crow made changes -
          Priority Original: Major [ 3 ] New: Minor [ 4 ]

          Basil Crow added a comment -

          This issue doesn't seem unique to Swarm; rather, it is a generic request for the Sonar plugin to push metrics to SonarQube from the agent to the master through JNLP and then from the master to SonarQube through TCP. This is definitely not a Swarm issue; rather, it would apply to any form of Jenkins agent (including SSH Build Agents). While it might be technically possible to implement such a system at the Remoting layer, I doubt the Remoting maintainer(s) would want to add SSH-like tunneling support to Remoting merely to satisfy this use case from 9 years ago. Nevertheless, if you feel strongly about this, please open an issue against the "Remoting" component to see if the Remoting maintainer(s) are interested in pursuing this further.

          Basil Crow added a comment - This issue doesn't seem unique to Swarm; rather, it is a generic request for the Sonar plugin to push metrics to SonarQube from the agent to the master through JNLP and then from the master to SonarQube through TCP. This is definitely not a Swarm issue; rather, it would apply to any form of Jenkins agent (including SSH Build Agents). While it might be technically possible to implement such a system at the Remoting layer, I doubt the Remoting maintainer(s) would want to add SSH-like tunneling support to Remoting merely to satisfy this use case from 9 years ago. Nevertheless, if you feel strongly about this, please open an issue against the "Remoting" component to see if the Remoting maintainer(s) are interested in pursuing this further.
          Basil Crow made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            ctrabold Christian Trabold
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: