Have your local Plastic client/server able to connect to the Plastic Cloud account.

Have at least one repo created in your organization's Plastic Cloud account.

Have an organization set up in Plastic Cloud.

Unity Cloud Build will regularly look for changes in this server. This will replicate from repos in Plastic Cloud, and push to the Git server. Together, these form a bridge from Plastic Cloud to Unity Cloud Build. You deploy these containers to a VM in Azure or Google Cloud. This package contains two Docker containers. We abandoned it in favor of a Jenkins build setup, because the Jenkins setup offered significantly shorter build turnaround times (from 30-60 minutes to 15 minutes for our project). This was used for internal development for a 6-month period. Should work, but occasional bugs require manual restart of the containers once every couple of weeks.

Unity's Cloud Build team implements Plastic-specific tooling or protocol support that enables it to watch and pull from remote Plastic repositories.

Once there is such an interface, then Unity Cloud Build will be able to connect to the Plastic Cloud repositories with their current implementation.

Codice Software implements a Git server interface, complete with account- and SSH-key-authentication, for Plastic Cloud.

If either of these happened, this project would become obsolete: Glue logic which enables Unity Cloud Build to build from Plastic Cloud repositories. Bridge from Plastic Cloud to Unity Cloud Build

Unity cloud build plastic