[JIRA] (JENKINS-41432) Perforce plugin doesn't always show changes in pipeline jobs

[phil.mcar...@cloudgine.com (JIRA)]

Title: Message Title

Phil McArdle commented on JENKINS-41432   Re: Perforce plugin doesn't always show changes in pipeline jobs I think I finally figured this out. I've solved it by not using the 'pin' parameter, and instead using the magic 'change' parameter, and using #head instead of now. I think I had two problems. I finally noticed this in the log: ... p4 changes //workspace/...@no___ - 15:01:13 p4 changes //workspace/...@now,6242 Which, obviously, no changes. In this scenario the previous build had been run at the default 'now' using pin: "${BUILD_CHANGELIST}" and the current build had been sent 6242 as a parameter by the polling job. So I tried switching to #head as the default for the BUILD_CHANGELIST parameter, except: ... p4 changes //workspace/...@#h___ - 16:07:13 p4 changes //workspace/...@#head,6247 16:07:13 16:07:13 Unintelligible revision specification ''. Again, same scenario, the previous build has been run successfully, manually, with #head as BUILD_CHANGELIST, and the current build has been sent 6247 from the polling job. So I tried switching to 'head', which works in the 'change' parameter, but pin doesn't accept that: 16:17:06 P4: Unable to find client/label/counter: head So I'm now using the 'change' parameter, and I'm using 'head' as the default for it. New output: 16:43:19 [ParallelStageName] (p4):cmd:... p4 changes //workspace/___ 16:43:19 [ParallelStageName] p4 changes //workspace/...@6251,6253 16:43:19 [ParallelStageName] 16:43:19 [ParallelStageName] Change 6253 on 2017/02/02 by phil.mcardle@PHIL-WS 'Test change 16:43:19 [ParallelStageName] ' 16:43:19 [ParallelStageName] Change 6251 on 2017/02/02 by phil.mcardle@PHIL-WS 'Test change 16:43:19 [ParallelStageName] ' Again, the previous build was ran with 'change' 'head', but for the purposes of calling p4 changes in the current build, perforce has stored 6251 instead of head or now, so I get proper change detection. This is working, as far as I can tell, completely perfectly within the parallel setup I have, with only one of 3 syncs sending changelog: true to checkout as described in the description. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.