Cloud Build Creating Multiple Workspaces in Perforce

We have Unity Cloud Build setup with Perforce including a workspace and user dedicated to UCB. However, whenever we go to build through UCB it creates an additional workspace.

Is this by design? If not, any ideas on how to prevent this from happening?

 

I am currently experiencing this very same issue: UCB requests a new workspace be created with every build and with Perforce's limit of 20 these workspaces are quickly exhausting all available accounts. Purging the accounts from P4 is OK as a temporal solution but ultimately defeats the whole purpose of automation.

Anyone got any clue as to why this is happening?

 

Bump - same problem here.

 

perforce.PerforceException: Can't add client - over license quota. Try deleting old clients with 'client -d'. License count: 20 clients used of 20 licensed. Additional users/clients may be obtained for evaluation purposes by visiting... http://www.perforce.com/eval

 

Hi all,

This is something that's definitely on our radar, there is some work that needs to be taken care of behind the scenes in order to support our deletion of workspaces on the Perforce instance as part of the build. There is no definite ETA for when that work will occur, so purging the created workspaces on a schedule is currently our suggested temporary solution.

I'll be sure to bookmark and update this thread as there is any further information on progress to share.

 

Thanks Chris - keep it up!

 

Hey unitychrism,

Any updates on this - its been a painful 3 months of deleting workspaces manually every time we exceed the 20 cap limit. Almost makes 'automated builds' feel manual! :-(

Thanks

 

Any updates on this? I still have this issue...

 

Having the same problem as well. Does it need extra configuration for that?

 

This is still a major issue for us as well. Has anybody found a solution?

Is there a script that can run on the P4 server to automatically delete them?

 

The original issue was that Cloud Build was creating a new workspace for every build. Now, it creates one workspace per platform and reuses it afterwards, which is, in my opinion, acceptable.

 

Would love to get to even work, but when I just kicked off a new build and got the issue. I set the workspace as "Main" originally, and then it keeps adding "Main-RandomNumberString" to the end of it.

Am I doing something wrong with the setup?



Update: Ended up writing my own python script to clean up the workspaces in a cron job. Was a major pain as I'm not a Linux expert, but finally got it working.

 

I can confirm that this has now been fixed. Been in contact with the cloud build engineers who helped out!

 

Hello, sorry to necro post, however this issue has resurfaced now, the cloud build bot no longer deletes the workspaces after it is done. I think it might happen if the build fails due to compile error, but not sure yet