• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • jenkinsfile-runner
    • None
    • jenkins master win10 on unc path

      Dear all,

       

      I have extremly low confidence that I selected the right component... sry...

      I did not yet nail down my observations perfectly, but my observations point towards.:

       

      When jenkins master uns on a UNC path:

      1.) running a pipeline from a git managed file only works when using https for transport, not via ssh.

      2.) downloading agent.jar does not work

      3.) starting a slave via ssh does not work

       

      I did compare to running jenkins from a unix machine using "regular" unix paths, there these 3 things work flawlessly. 

       

      Does anyone experience similar issues? Is this a known problem? Would it help if I compare the win10 UNC vs win10 "c:\jenkins"?

       

      Thanks in advance,

      Franz

          [JENKINS-68701] jenkins master on unc path vs normal path

          franz haas added a comment -

          Dear all, 

           

          i changed the starting of the jenkins master to starting from a non unc path. Now i can download agent.jar, and start ssh slaves.

           

          I didnt check for git+ssh checkouts for pipeline job files...

           

          Thanks,

          Franz

          franz haas added a comment - Dear all,    i changed the starting of the jenkins master to starting from a non unc path. Now i can download agent.jar, and start ssh slaves.   I didnt check for git+ssh checkouts for pipeline job files...   Thanks, Franz

            Unassigned Unassigned
            fhaa franz haas
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: