Issue Details (XML | Word | Printable)

Key: BAM-924
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Brydie McCoy [Atlassian]
Reporter: Ola Sætrom
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Bamboo

Perforce client error forces full checkout/build

Created: 27/Feb/07 03:40 PM   Updated: 01/Apr/08 07:05 PM
Component/s: Build Triggers, Repository (Other)
Affects Version/s: 1.0
Fix Version/s: 2.0 beta 3, 2.0

Time Tracking:
Not Specified

Environment: Bamboo 1.0 on windows using perforce as source repository, and change-polling

Participants: Ajay Sridhar [Atlassian], Brydie McCoy [Atlassian], Edwin Wong [Atlassian] and Ola Sætrom
Since last comment: 40 weeks ago
Number of comments: 5
Internal Priority: 3. Medium
Internal Work Bucket: Confirmed (investigating)
Labels:


 Description  « Hide
abstract from bamboo log:

[...]
INFO | jvm 1 | 2007/02/27 22:12:19 | 2007-02-27 22:12:18,996 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:19 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:19 | 2007-02-27 22:12:19,230 INFO [BAM::BuildChangeDetector] [PerforceSyncCommand] Executing perforce sync command:
INFO | jvm 1 | 2007/02/27 22:12:19 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt sync //oslsatoladt/main/common/...
INFO | jvm 1 | 2007/02/27 22:12:19 | 2007-02-27 22:12:19,230 INFO [BAM::BuildChangeDetector] [PerforceSyncCommand] Executing perforce sync command:
INFO | jvm 1 | 2007/02/27 22:12:19 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt sync //oslsatoladt/main/common/...
INFO | jvm 1 | 2007/02/27 22:12:19 | 2007-02-27 22:12:19,480 INFO [TEST-DEF:Error Pump] [RedStreamToListPumper] //oslsatoladt/main/common/... - file(s) up-to-date.
INFO | jvm 1 | 2007/02/27 22:12:20 | 2007-02-27 22:12:20,496 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:20 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:20 | 2007-02-27 22:12:20,496 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:20 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:21 | 2007-02-27 22:12:21,746 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:21 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:21 | 2007-02-27 22:12:21,746 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:21 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,012 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:23 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,012 INFO [BAM::BuildChangeDetector] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:23 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [Command] err>Perforce client error:
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [Command] err> Connect to server failed; check $P4PORT.
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [Command] err> TCP connect to perforce.osl.org:1666 failed.
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [Command] err> connect: perforce.osl.org:1666: WSAEACCES
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 WARN [BAM::BuildChangeDetector] [PerforceClientCommand] Perforce client root cannot be found. Returning null;
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [DefaultBuildChangeDetector] The source code directory (null\main\common) for build "test - Default" does not exist, requires full checkout.
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [PerforceSyncCommand] Executing perforce sync command:
INFO | jvm 1 | 2007/02/27 22:12:23 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt sync -f //oslsatoladt/main/common/...
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [PerforceSyncCommand] Executing perforce sync command:
INFO | jvm 1 | 2007/02/27 22:12:23 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt sync -f //oslsatoladt/main/common/...
[...]

Every once and again the p4 commando fails due to client error. This causes the a full checkout from perforce with, and a complete build. This is mildly annoying since it causes lots of unnecessary builds, and lots of builds without changelists. This complete checkout destroys the changlist history in a given plan.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Edwin Wong [Atlassian] added a comment - 27/Feb/07 06:19 PM
Hi Ola,

Just a few questions to help us nail down the problem:

I was just wondering if Bamboo actually checked out your source code? From the logs, it would seem that Bamboo failed to connect to the Perforce repository altogether. Has the build ever completed successfully?

Also, are you running Bamboo as a Windows service?

Cheers,
Edwin


[ Permlink | « Hide ]
Ola Sætrom added a comment - 28/Feb/07 02:39 AM
Hi Edwin,

It seems like Bamboo manages to check out the code when performing the full sync. Log snippet:

INFO | jvm 1 | 2007/02/27 22:12:23 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [Command] err>Perforce client error:
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [Command] err> Connect to server failed; check $P4PORT.
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [Command] err> TCP connect to perforce.osl.org:1666 failed.
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [Command] err> connect: perforce.osl.org:1666: WSAEACCES
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 WARN [BAM::BuildChangeDetector] [PerforceClientCommand] Perforce client root cannot be found. Returning null;
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [DefaultBuildChangeDetector] The source code directory (null\main\common) for build "test - Default" does not exist, requires full checkout.
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [PerforceSyncCommand] Executing perforce sync command:
INFO | jvm 1 | 2007/02/27 22:12:23 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt sync -f //oslsatoladt/main/common/...
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,246 INFO [BAM::BuildChangeDetector] [PerforceSyncCommand] Executing perforce sync command:
INFO | jvm 1 | 2007/02/27 22:12:23 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt sync -f //oslsatoladt/main/common/...
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,402 INFO [TEST-DEF:Output Pump] [StreamToListPumper] [TEST-DEF] //depot/proj/common/MAIN/Codeline.html#2 - refreshing f:\p4\main\common\Codeline.html
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,402 INFO [TEST-DEF:Output Pump] [StreamToListPumper] [TEST-DEF] //depot/proj/common/MAIN/all-source/.p4ignore#1 - refreshing f:\p4\main\common\all-source\.p4ignore
INFO | jvm 1 | 2007/02/27 22:12:23 | 2007-02-27 22:12:23,402 INFO [TEST-DEF:Output Pump] [StreamToListPumper] [TEST-DEF] //depot/proj/common/MAIN/all-source/pom.xml#3 - refreshing f:\p4\main\common\all-source\pom.xml

[...] lots of code refreshing [...]

INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,402 INFO [TEST-DEF:Output Pump] [StreamToListPumper] [TEST-DEF] //depot/proj/common/MAIN/src/site/resources/images/sourcebg.jpg#1 - refreshing f:\p4\main\common\src\site\resources\images\sourcebg.jpg
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,402 INFO [TEST-DEF:Output Pump] [StreamToListPumper] [TEST-DEF] //depot/proj/common/MAIN/src/site/site.xml#2 - refreshing f:\p4\main\common\src\site\site.xml
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,402 INFO [BAM::BuildChangeDetector] [PerforceChangesCommand] Executing perforce changes command:
INFO | jvm 1 | 2007/02/27 22:12:24 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt changes -s submitted //oslsatoladt/main/common/...@2007/02/27:22:06:35,2007/02/27:22:12:24
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,402 INFO [BAM::BuildChangeDetector] [PerforceChangesCommand] Executing perforce changes command:
INFO | jvm 1 | 2007/02/27 22:12:24 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt changes -s submitted //oslsatoladt/main/common/...@2007/02/27:22:06:35,2007/02/27:22:12:24
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,637 ERROR [BAM::BuildChangeDetector] [DefaultBuildChangeDetector] Error: Source code repository does not exist for build "test - Default" following checkout.
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,637 INFO [BAM::PipelineSelector] [PipelineSelector] Placing build results BuildResults: TEST-DEF-0
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,652 INFO [BAM:Default Queue:BuildExe] [PrepareBuildTask] Starting build: BuildResults: TEST-DEF-0
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,652 INFO [BAM:Default Queue:BuildExe] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:24 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,652 INFO [BAM:Default Queue:BuildExe] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:24 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,652 INFO [BAM::PipelineSelector] [PipelineSelector] Found queue for build results BuildResults: TEST-DEF-3
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,918 INFO [BAM:Default Queue:BuildExe] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:24 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:24 | 2007-02-27 22:12:24,918 INFO [BAM:Default Queue:BuildExe] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:24 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:25 | 2007-02-27 22:12:25,183 INFO [BAM:Default Queue:BuildExe] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:25 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:25 | 2007-02-27 22:12:25,183 INFO [BAM:Default Queue:BuildExe] [PerforceClientCommand] Executing perforce client command:
INFO | jvm 1 | 2007/02/27 22:12:25 | "c:\Program Files\Perforce\p4.exe" -u satola -p perforce.osl.org:1666 -c oslsatoladt client -o
INFO | jvm 1 | 2007/02/27 22:12:25 | 2007-02-27 22:12:25,512 INFO [BAM:Default Queue:BuildExe] [SubmittedBuildFuture] Task class com.atlassian.bamboo.build.pipeline.concurrent.SubmittedBuildFuture for TEST-DEF is done! Cancelled: false
INFO | jvm 1 | 2007/02/27 22:12:25 | 2007-02-27 22:12:25,512 INFO [BAM:Default Queue:BuildExe] [AbstractBuilder] Starting to build 'test - Default'

[...] the build completes successfully

So the build completes successfully every time.

I've tried running Bamboo both as a Windows service and in a console, but this happens in both cases.

Thanks,
Ola


[ Permlink | « Hide ]
Ajay Sridhar [Atlassian] added a comment - 25/Mar/07 09:29 PM
Hi Ola,

Sorry for the late reply and we will try to resolve this issue soon.

Cheer,
Ajay


[ Permlink | « Hide ]
Brydie McCoy [Atlassian] added a comment - 05/Apr/07 12:37 AM
Hi Ola,

It appears that bamboo was interpreting the failed client command incorrectly when it is trying to retrieve the source code directory (the client root).

This should no longer be an issue as we have changed the way Bamboo stores the source code repository. As of 1.0.4 Bamboo will cache this so it will no longer be calling the perforce server to retrieve the information.

You can find more information about this fix here: http://jira.atlassian.com/browse/BAM-1078

Cheers,
Brydie


[ Permlink | « Hide ]
Brydie McCoy [Atlassian] added a comment - 25/Feb/08 09:16 PM
Hi,

In 2.0 bamboo will set the source code directory itself rather than using the directory specified in the perforce client.
This means that this is no longer an issue.

Brydie
Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators