[#BAM-2362] Can't edit existing perforce repository plan to a new P4 workspae

Bamboo

Can't edit existing perforce repository plan to a new P4 workspae

Created: 11/Mar/08 08:08 PM Updated: 25/Mar/08 05:34 PM

Component/s:

Repository (Perforce)

Affects Version/s:

2.0 beta 4

Fix Version/s:

2.0 beta 8

Time Tracking:

Not Specified

Participants:	Ajay Sridhar [Atlassian], Brydie McCoy [Atlassian] and Scott Marshall
Since last comment:	28 weeks ago
Company:	citrixonline.com (Find related issues)
Number of comments:	2
Internal Priority:	2. High
Internal Work Bucket:	Investigating
Labels:

Description

« Hide

From http://forums.atlassian.com/thread.jspa?messageID=257276266#257276266 -

Bamboo 2.0 Beta4 does not seem to accept a new P4 Workspace name once the build plan is created. I have tried to enter a new exisiting workspace name when creating a new build plan as well as when updating an existing one and I get an error saying "Client was not found on the perforce server". It might work if I restart the Bamboo server but only the first time. Is this a known issue with the Beta4 build? Is there a work around for this?

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Brydie McCoy [Atlassian] added a comment - 24/Mar/08 11:50 PM

Hi Scott,

I'm just checking to see whether or not you managed to get this issue resolved?

Cheers,
Brydie

[ Permlink | « Hide ]

Scott Marshall added a comment - 25/Mar/08 01:44 AM

By changing the user who runs the Bamboo Server service under Win32, I was able to add new p4 workspace names. I think someone mentioned this in the thread I created on the forum. I think the problem is that the system account does not have credentials to run the p4 client command correctly.