Currently Unity Build Automation doesn’t seem to support Perforce’s Helix Core Cloud platform.
When I plug in the source control URL it errors and reports Invalid URL. I have verified that the URL is correct (works fine in multiple other tools) and this is some sort of problem on Unity’s side.
Seeing as these Helix Core Cloud repositories are also unsupported in the unity editor. ( see Perfoce Cloud Host in Unity ) and has been for quite a while, I assume that maintaining perforce support is not a priority for Unity at this point. Especially since it competes with their in-house version control product.
Various other teams I work with have used Unity Build Automation and really like the tool. Is support of Helix Core Cloud planned for Unity Build Automation?
There isn’t a reason why we shouldn’t be supporting Helix Core Cloud hosted P4 repos.
I’d suggest opening up a support ticket so that our support team can dig into this and figure out what is going on and why we are getting an invalid url response.
While you wait for a response I looked into our logs and I didn’t see any error messages over the past two weeks related to “helixcore.io”. This might be coming from the UI and not from our service itself. What I would suggest is using our APIs to attempt the source control configuration yourself.
In the DevOps dashboard under Settings there is an API key. Take that API key and you’ll want to make a PUT request to:
https://build-api.cloud.unity3d.com/api/v1/orgs/{orgid}/projects/{projectid}
with the body:
{
"settings": {
"scm" : {
"type": "p4",
"url": "ssl:....helixcore.io:1666",
"user": "username",
"pass": "pass",
"authType": "ticket"
}
}
If this works and doesn’t return an error then there is an issue with the URL validation on the Cloud Dashboard. If it doesn’t work, you can at least share this info with the support team when they start working your ticket.
1 Like
Thanks for the quick reply!
The API approach seems to have worked without error. When we looked back at the dashboard after, the URL info seems to have shown up. Though, the URL field appeared to be missing the ssl: at the start. Previously, when I plug in the URL with no ssl: (e.g. projectname.helixcore.io:1666 ) is also threw an error.
Also it looks like the password field isn’t showing up despite having appeared set in the API response:
This might be a clue to the possible front end bug.
Further when I attempt to set up a configuration, it errors with Error: failed to fetch client workspaces
I am pretty sure we have the permissions set correctly on the perforce side.
This at least moves it forward. I would definitely open up the support ticket so that we can get the front-end and back end work needed to resolve this identified.
Could you please try configuring build targets again in the UI. You should be able to retrieve the workspace now that I’ve upgrade our backend service to use the 2024.4 perforce client. Our Mac Silicon machines already have the 2023.2 perforce client so you should be able to build on those today. Next week I’ll be upgrading the Windows machines to be running 2024.2
