Perforce plugin is failing for me when Perforce returns "no file(s) at that changelist number" errors. The plugin throws an exception for that error but doesn't throw an exception for "file(s) up-to-date", which is also a Perforce "error". Both "errors" are really harmless. Has anyone else seen that case? It can happen if the Perforce client has multiple mappings, one of which has had all of its files deleted on the Perforce server. I could just remove the dead mapping but my Perforce client mappings are managed by IC Manage so it might just come back the next time someone updates the configuration.
-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/37a57423-708b-41b9-b624-169aa5a4f869%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
