|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Thanks, Rob. I've tried to use a lower version of this perforce plugin v1.2.9. It won't give this error. Particularly, when using v1.2.9, the "p4 -G where" command right before the error is like this:
===
[dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -s sync //jenkinspilot2_test_p4-161040911/...@362136
===
, instead of:
===
[dev] $ /usr/local/bin/p4 -P 6BD4xxxxxxxxxxxxxxxxxxxxxxx -s sync //...
===
I find this very similar to a bug related to p4 where parsing that was fixed in v1.2.9, and it's indeed a working version for us.
And if the breakage was caused by a trigger that worked with 2012.1 but wouldn't work with 2012.2, any suggestion of how to identify it?
Thanks!