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

Support -cert and -noCertificateCheck with -webSocket

    XMLWordPrintable

Details

    • Improvement
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • remoting
    • None

    Description

      The only way to make the agent connect to a Jenkins master with a self-signed HTTPS certificate seems to be by adding the certificate in the host. This is a problem with the Docker image because of the need to extend it.

      The options -cert and -noCertificateCheck is already present in the remoting library, but not available for use with the -webSocket.

      Attachments

        Issue Links

          Activity

            felipecassiors Felipe Santos created issue -
            felipecassiors Felipe Santos made changes -
            Field Original Value New Value
            Link This issue is related to JENKINS-64758 [ JENKINS-64758 ]
            felipecassiors Felipe Santos made changes -
            Remote Link This issue links to "docker-inbound-agent#17 (Web Link)" [ 26478 ]
            felipecassiors Felipe Santos made changes -
            Remote Link This issue links to "docker-inbound-agent#38 (Web Link)" [ 26479 ]
            felipecassiors Felipe Santos made changes -
            Remote Link This issue links to "kubernetes-plugin PR #941 (Web Link)" [ 26480 ]

            People

              jthompson Jeff Thompson
              felipecassiors Felipe Santos
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: