[#BAM-1406] Perforce change logs not picked up due to update returning too many results.

Bamboo

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

Created: 28/Jun/07 11:21 PM Updated: 04/Jul/07 01:28 AM

Component/s:

Repository (Perforce)

Affects Version/s:

1.1.2

Fix Version/s:

1.2

Time Tracking:

Not Specified

Participants:	Ajay Sridhar [Atlassian], Brydie McCoy [Atlassian] and Mark Chaimungkalanont [Atlassian]
Since last comment:	1 year, 27 weeks, 1 day ago
Number of comments:	1
Internal Work Bucket:	Confirmed
Labels:

Description

« Hide

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

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Brydie McCoy [Atlassian] added a comment - 04/Jul/07 01:00 AM

Hi,

I have changed the way perforce retrieves the changelist information to ensure that it does not retrieve any more than it needs to retrieve. This should solve the 'request too large' errors and also reduce memory usage by the perforce server.

The changes will be included in the next release.

Cheers,
Brydie