[JIRA] (JENKINS-61745) Scan multibranch with date range or dop '@now'

[kwi...@perforce.com (JIRA)]

Title: Message Title

Karl Wirth created an issue   Jenkins / JENKINS-61745 Scan multibranch with date range or dop '@now' Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2020-03-30 15:53 Environment: p4-plugin 1.10.9 Priority: Blocker Reporter: Karl Wirth When scanning for changes in multibranch pipelines we use p4 changes -m1 //Path/...@now. This is triggering a similar resource behavior to: JENKINS-57870 For example with a big dataset in the multibranch scan log we see: p4 changes -m1 //Path/branch/...@now Request too large (over 500000); see 'p4 help maxresults'. ERROR: [Mon Mar 30 13:07:05 CEST 2020] Could not fetch branches from source d5fe37f7-6c40-4111-af23-d4f539fec120 com.perforce.p4java.exception.RequestException: Request too large (over 500000); see 'p4 help maxresults'. When checking this at the command line we see that limiting the query or dropping '@now' works: $ p4 changes -m1 //path/branch/...@now Request too large (over 500000); see 'p4 help maxresults'.$ p4 changes -m1 //path/branch/...@2020/03/30 Request too large (over 500000); see 'p4 help maxresults'.$ p4 changes -m1 //path/branch/... Change 62552 on 2020/03/30 by user@PC1 'CL Description'$ p4 changes -m1 //path/branch/...@52552,62552 Change 62552 on 2020/03/30 by user@PC1 'CL Description' Would be great if we could either drop the usage of '@now' or restrict to the last n changes.     Add Comment   This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205574.1585583601000.3002.1585583640094%40Atlassian.JIRA.