|
||||||||
|
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/d/optout.
The timestamper seems a bit intrusive and a lot of fixes have been done that are not in the latest LTS version.
If i have a big build across multiple sites then i would want to upload the time the Perforce actions ( sync) takes to determine how long does a full sync of stream X takes on site A,B,C,D
I can then get IT to look at optimizing the distributed Perforce proxies around our sites.
A stream or client specs might be too wide or someone might have added a very large file in a wrong place causing a knock on effect.
I know i could write a groovy script to post process the log to pull the durations but it seems a lot of work if the plugin could just expose this....