|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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/groups/opt_out.
The git plugin is completely different from the perforce plugin, so I'm not sure what bearing that has.
That link seems to describe the API for Perforce's "Stream" functionality, which is more or less just a replacement for client mappings.
I am referring to being able to parse and filter log output as it is captured in order to prevent out of memory exceptions that would otherwise occur. I do not know if the p4java API has the ability to filter results in this way.
Regardless, none of this has anything to do with this ticket. While switching over to the official p4java api would resolve the issue, I don't believe it is a viable solution at this time.