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

Multibranch scan uses backslash instead of slash when scanning for Jenkinsfile

XMLWordPrintable

      Starting with version 2.14 of the multibranch plugin, the scanning of a branch is done on Windows using a backslash "\';  This cause perforce to fail when trying to find the Jenkinsfile, and the multibranch project ends up finding nothing.

       

      Starting in 2.14 (also tested with 2.15 and 2.16), I see this:

       

       
      [jeu. août 31 10:25:40 EDT 2017] Starting branch indexing...
      (p4):cmd:... p4 streams //beacon-osdk/...
      p4 streams //beacon-osdk/...
      
      (p4):stop:4
      (p4):cmd:... p4 client -o jenkins-master
      p4 client -o jenkins-master
      
      (p4):stop:4
      (p4):cmd:... p4 info
      p4 info
      
      (p4):stop:5
      (p4):cmd:... p4 files //beacon-osdk/v5.0-main\Jenkinsfile
      p4 files //beacon-osdk/v5.0-main\Jenkinsfile
      
      //beacon-osdk/v5.0-main\Jenkinsfile - no such file(s).
      
      (p4):stop:6
      ‘Jenkinsfile’ not found
      

       

      Whereas in 2.13, I had this:

       

       

      [jeu. août 31 10:25:40 EDT 2017] Starting branch indexing...
      (p4):cmd:... p4 streams //beacon-osdk/...
      p4 streams //beacon-osdk/...
      (p4):stop:4
      (p4):cmd:... p4 client -o jenkins-master
      p4 client -o jenkins-master
      (p4):stop:4
      (p4):cmd:... p4 info
      p4 info
      (p4):stop:5
      (p4):cmd:... p4 files //beacon-osdk/v5.0-main/Jenkinsfile
      p4 files //beacon-osdk/v5.0-main/Jenkinsfile
      //beacon-osdk/v5.0-main/Jenkinsfile#1 - add change 98200 (text)
      (p4):stop:6
       ‘Jenkinsfile’ found
      

       

       

       

       

            vaimr Denis Saponenko
            gpetit Gaspard Petit
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: