Perforce change logs not picked up due to update returning too many results.

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • 1.2
    • Affects Version/s: 1.1.2
    • Component/s: Repository (Perforce)
    • None 

      2007-06-28 13:36:25,458 INFO [BAM::BuildChangeDetector] [PerforceChangesCommand] Executing perforce changes command:
/usr/local/bin/p4 -u XXXX -p 10.100.1.16:1666 -c XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2007-06-28 13:36:26,137 INFO [BAM::BuildChangeDetector] [Command] err>Request too large (over 50000); see 'p4 help maxresults'.

      The error went away after increasing our max results on the perforce server, and restarting bamboo. If all you are trying to do is get the most recent change number, you can specify a max result and avoid this error altogether.

      As per, https://support.atlassian.com/browse/BSP-148

              Assignee:
              bmccoy
              Reporter:
              AjayA
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: