getClientHead without range

[kjs104901]

Our Perforce server has been operational since July 2, 2013, and the current changelist number is 1524832.

Normally, using changes -m is efficient for both users and build machines due to our optimization settings.
(For more details, see Server performance related to 'p4 changes').

However, retrieving changes for a specific client and revision is significantly slower
(changes -m1 //clientname/...@Rev).
This slowdown affects the plugin's ability to determine the latest changelist number for clients.

I believe that setting a revision range for changes is not essential, and omitting it could enhance performance.
According to the documentation, optimizations are most effective when not restricted by revision specifications.

I have already implemented this change in our Jenkins setup, and it has shown positive results.

Before

After

Testing done

Submitter checklist

Edit tasklist title

Beta Give feedback Tasklist Submitter checklist, more options

• Rename
• Copy markdown
• Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel Delete

1. Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!

   Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
2. Ensure that the pull request title represents the desired changelog entry

   Ensure that the pull request title represents the desired changelog entry
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
3. Please describe what you did

   Please describe what you did
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
4. Link to relevant issues in GitHub or Jira

   Link to relevant issues in GitHub or Jira
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
5. Link to relevant pull requests, esp. upstream and downstream changes

   Link to relevant pull requests, esp. upstream and downstream changes
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

   Ensure you have provided tests - that demonstrates feature works or fixes the issue
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove

Add item to Submitter checklist

[skumar7322]

Thanks @kjs104901 for creating this PR to improve P4-Plugin. Will take up this in our next release.