[JIRA] (JENKINS-41432) Checkout step doesn't show changes

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

Title: Message Title

Phil McArdle updated an issue   Jenkins / JENKINS-41432 Checkout step doesn't show changes Change By: Phil McArdle I have two pipeline jobs which are identical in the raw XML view, the newer of which experiences this problem when trying to fetch P4 changes. In the job, I use the checkout step with PerforceScm, instead of using p4sync, because I need access to checkout's changelog: and poll: variables, which p4sync doesn't seem to expose. Use case: I sync the same depot path to multiple workspaces across multiple slaves in parallel for different tests, but if I don't use the checkout step with changelog: false, I will get identical sets of changes for as many times as I call p4sync. I poll on a different job, but also using the checkout step, as the p4sync step doesn't expose the polling filter rules. This job is XML identical to an earlier job, and the newer one has the same problem - no changes seen in the UI or the API. (As an aside, when running perforce in the checkout step, I'm not sure it obeys poll:false but it's difficult to tell because the polling might have been setup from running p4sync once?) -To "fix" the new job, I replace every instance of checkout with a p4sync with otherwise identical parameters, run the job once, and then replace them with checkout again. After this, the job reports changes properly every time.- This worked for a while, but once again both of the 'new' jobs using checkout don't report changes in the UI, though the console log says "saving built changes." and the command output as seen in the log sees the changes. To clarify some more, I have 3 stages that run in parallel, all of which call checkout, and two of which send updateChangelog: false. In my latest case of it not working, I set all 3 stages to updateChangelog: true, ran it once, got 3 sets of identical changes, set 1 stage to true and the other 2 stages to false again, ran it again and it was fine. I'm sorry I can't report a better bug for this. 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.