applenaut Posted November 23, 2016 Report Share Posted November 23, 2016 Hello, We're using Unity Cloud Build. Is there a way to integrate Plastic with it? Thanks. Link to comment Share on other sites More sharing options...
manu Posted November 24, 2016 Report Share Posted November 24, 2016 Yes! Using Gitserver: https://www.plasticscm.com/gitserver/ You'll need an on-premise Plastic SCM server for this. GitServer will publish your Plastic SCM repositories as Git ones, you can then use the Git spec git://YourPlasticServer/TheRepoName for the Plastic repo in order to connect it with Unity Cloud Build. Best, Manu. Link to comment Share on other sites More sharing options...
Mikael Kalms Posted December 17, 2016 Report Share Posted December 17, 2016 For those users who want to encourage Unity to implement native Plastic support for UCB, here is the main thread in the Unity3D forums: https://forum.unity3d.com/threads/plastic-scm-support-in-ucb.268999/ My interest in this is to enable us to run all our development services in hosted solutions at a reasonable price. RIght now, as long as we use Plastic in any form we need to run one part of it on AWS (either the main Plastic server, or a Plastic replica, or a Jenkins CI setup). Link to comment Share on other sites More sharing options...
manu Posted December 19, 2016 Report Share Posted December 19, 2016 Thank you Mikael for pushing this inside the Unity forums, really appreciate it. We hope to have UCB support for Plastic SCM too. Link to comment Share on other sites More sharing options...
Mikael Kalms Posted March 17, 2017 Report Share Posted March 17, 2017 For those interested, we have built a bridge from Plastic Cloud to UCB that we run in a VM in Azure: https://github.com/falldamagestudio/plastic-cloud-to-ucb/ It works, and has appropriate authentication, but takes a lot of effort to configure correctly. Link to comment Share on other sites More sharing options...
Mikael Kalms Posted March 26, 2018 Report Share Posted March 26, 2018 We have migrated from UCB to a Jenkins setup that we run on VMs in Google Compute Engine. Main reasons for migrating: shorter build turnaround times, Plastic changeset IDs visible through the entire build process, more flexibility in build configuration. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.