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

Add support of Remoting connections to masters without Web UI

    XMLWordPrintable

Details

    • Remoting 3.34

    Description

      Currently Remoting agents always require Jenkins master to have a Tcp Agent Listener endpoint. It complicates usage of Remoting with CloudAPI-provided agents together with Jenkinsfile Runner which does not have a fixed Web UI port.

      I propose to add new options to Remoting so that it can connect without polling metadata from the master

       

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-59094 Agent tunnel connection issues after ugrading Jenkins to 2.191

          • Major - Major loss of function.
          • Resolved
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-28499 tcpSlaveAgentListener not found

          • Blocker - Blocks development and/or testing work, production could not run.
          • Reopened

          Task - A task that needs to be done. JENKINS-54427 Support sidecar containers

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          links to

          Web Link https://github.com/jenkinsci/remoting/pull/286

          Activity

            People

              jthompson Jeff Thompson
              oleg_nenashev Oleg Nenashev
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: