This fix provides the 2 times it need.
How long the prepare(cleanup) took and how long the sync took

done git pull request for the fix

Reposted here...

I need to understand why the p4-plugin.properties file is necessary?
For the moment I have commented it out, I'll look at it tomorrow (it 22:00 in the UK).

I am concerned that an extra file might break other users builds or even appear in their releases!

Reason was that I couldn't figure out any env variables that the plugin set to find the CL that was synced to. ( not unshelved)

BTW what timezones are you in? I work near Cambridge UK

I work in Wokingham, so only down the road.

You could use TagAction, it was designed for labeling builds, but could be a way to stash the value. I'll have a think, but getting a bit too late for me.

the latest version now shows duration

... duration: 0m 5s
SCM Task: restoring all missing and changed revisions.
... [list] = reconcile [-n, -e, -d, -f, -m]
... duration: 2m 0s
SCM Task: syncing files at change: 74939
... sync /var/lib/jenkins/workspace/__l1phy_int_mlb_10/...@74939
... force update false
... bypass have false
... duration: (226ms)
SCM Task: unshelve review: 61023
... sync /var/lib/jenkins/workspace/__l1phy_int_mlb_10/...
... unshelve -f -s 61023 /var/lib/jenkins/workspace/__l1phy_int_mlb_10/...
... revert -k /var/lib/jenkins/workspace/__l1phy_int_mlb_10/...
... duration: 0m 1s