We’ve had quite a few requests for this over the last few years, so we’re happy to announce that Cloud Build now supports using Plastic SCM for source control!
Plastic SCM had previously provided a workaround to get Cloud Build working with your Plastic repositories by using Gitlab as an intermediary, this was a pretty ingenious idea but it did add an extra layer of complexity and it meant that users were missing out on a few of the cool features in Plastic SCM - like large file support.
We hope that setting up and using Plastic SCM with Cloud Build is simple and user-friendly enough that you won’t really need much instruction, but the Unity Manual has the details here: Unity Build Automation
As always, please reach out to our support team if you encounter issues or have questions!
Amazing news. Thank you guys for adding Plastic Support to UCB. Unfortunately, we have an issue with it. Our project is quite big and we currently have around 32k change sets in our Plastic. After selecting a Repository for the target, branches were supposed to load, but instead we receive an Error message: “Error getting Plastic branches: stdout maxBuffer exceeded”. Is there a workaround or is there a way to fix the issue ?
This should be easy enough to fix. For the moment, if you submit a support ticket and a list of configurations you want to build for then we can manually configure your project. You can also bypass the frontend to manually configure it yourself using the build API if you want.
This is great! We are running into one issue though. After I select the repo, the branch dropdown is never populated with anything. In fact there is no dropdown. Is there something that we need to configure on our branches to get them to show up or is this a different issue?
That’s pretty weird - I had a look at your project and I wasn’t able to replicate this issue, the branches showed up without issue. Which browser are you using?
Never mind, I was able to replicate this. Looks like this is an issue which only shows up when you’re adding a new build target, on a project which is already configured. You can edit your existing build targets just fine and creating new projects also works without issue. Not really sure what’s going wrong here but I’ll try to get a fix released ASAP.
In the meantime you should still be able to use your project by updating the existing build targets. If necessary then I believe you could also create new build targets by copying the existing ones and then modifying them from there.
Glad to hear this was reproducible! If it helps, we were actually updating an existing build target when we ran into this, not creating a new one, so we still don’t have a way to get that running. That said, we’ll hold tight until you get a fix in!
Thank you, thank you, thank you for finally adding plastic support to Unity Cloud Build! This is such an important feature for Plastic SCM users and especially for Plastic Cloud users since cloud version didn’t have a git server feature. We had a workaround where we had a separate git repository and would jut sync plastic to git and then use git for Unity CLoud Build. Already switched our UCB projects to Plastic connector, works great so far!
WOW
Why wasn’t that featured in Unity Blog as previous plastic scm related news were ?
That’s fantastic! Can’t wait to try it!!
Edit after testing:
It’s working very well, happy not to have to deal with git-sync anymore!
Feedbacks regarding the setup in unity account :
I was struggling to understand that Repo:Other meant that I was going to setup in the target builds afterwards (I do the tutorial step by step, not reading it entirely before starting it). So I was stuck on that trying to understand what I had done wrong.
Maybe using a better wording that ‘Other’ might help easily confusable people like me ^^
Also: the word ‘username’ is used to describe plastic login, where we only have ‘email’, which can also be confusing (I was looking for an username on my account but didn’t had one of course.
Other than that, it seems to work all good, that’s really great. It’s been a long time an Unity initiative didn’t made me that happy, thanks a lot, truly
I’m having trouble connecting my company’s self-hosted server to cloud build.
The initial connection works fine until entering the user name/password:
“Repo is not accessible. Please check your URL and repo settings.”
I’ve tried with several of our user accounts (incl. the admin account), but non of them worked.
Do I need to specify the repo in the url? Like: repo/my-sub-repo@ssl://serverurl.com:8088
So far, serverurl.com:8088 seems to be the only way to get to the user credential prompt.
The Plastic client has no problems connecting to our server over the internet, so I can rule out a network issue.
I am trying to setup Cloud build with Plastic and I am also running into the same issue
“Repo is not accessible. Please check your URL and repo settings.”
We managed to get it working soon after my initial post. The issue was that Cloud Build expects a valid SSL certificate that matches your URL. You can get one from Lets Encrypt and configure your server to use it.
Hi, I am trying to use this but it does not seem to work.
I entered server name xyz@cloud and user name and password with type ‘password’ selected. I used the same login that I use to login plastic (which is also the unity login). But it does not connect.
Edit: I tried it again a week later and it worked now.
Hey, having the same issue here. Fresh project and plastic repo, if I choose an incorrect plastic repo URL it won’t let me so I am guessing [projectname] @anon_13126019 is correct. I created a user just for this, and also, just to test it, used my Unity account that is linked to plastic, same issue. Are there any other requirements not listed in the documentation?
Accessing the repo via Plastic Client works fine btw.
