-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
It would be very good to expose the time the perforce plugin took to perform its actions as env variables.
We can then track down clients specs that are taking too long to sync (because they are too big) or proxies that have not been set up currently etc.
I can then take these variables and post process them.
Timestamper plugin might help, assuming there's sufficient build log output by the plugin.
Also, should be easy to write a plugin that lists time spent per build phase/step, similar to Metrics Plugin's waiting in queue/executing info.
(What is it about Perforce that requires weird features like this?)