Starting with version 1.7.4 of the P4 Plugin, the scanning of a multi-branch pipeline is done on Windows using a backslash "\' when looking for the Jenkinsfile; This cause perforce to fail when trying to find the Jenkinsfile, and the multibranch project ends up finding nothing.
Starting in 1.7.4 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 1.7.3 and previous versions, 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
- relates to
-
JENKINS-46566 Multibranch scan uses backslash instead of slash when scanning for Jenkinsfile
-
- Closed
-
