• Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • p4-plugin
    • 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.

          [JENKINS-24740] Expose duration of sync in ENV

          Daniel Beck added a comment -

          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?)

          Daniel Beck added a comment - 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?)

          Morne Joubert added a comment -

          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....

          Morne Joubert added a comment - 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....

          Additionally, you can create separate tool that will just analyze build logs with existed timestamps and then provide any info you want for your it.

          Kanstantsin Shautsou added a comment - Additionally, you can create separate tool that will just analyze build logs with existed timestamps and then provide any info you want for your it.

            Unassigned Unassigned
            mornejoubert Morne Joubert
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: