Plastic cloud for distributed team

[Joseph]

I am not sure about this, I am coming from a background using Github/Bitbucket/Gitlab and now wanted to switch to PlasticSCM to test working with Unity and everything.

That said, we chose to work with Plastic Cloud, so we all push to a repository there. 
We are trying to have some workflow in place, saw a lot of videos about "Perfect Workflow" and "MergeBots". How does this integrate with Cloud?
And if it does not, how can we have something setup that works and also syncs with Cloud?

[Héber]

Hi Joseph,

I'm not sure if I'm understanding your needs.

Here you have a cloud edition guide that explains how to set it up and to chose a workflow:

https://www.plasticscm.com/documentation/cloud-edition/plastic-scm-version-control-cloud-edition-guide#WorkdistributedwithPlastic

I'd recommend the centralized workflow unless you have a bad network.

Let me know if you have any questions.

 

Best,

Héber.

[Joseph]

Hi Héber, I have already setup the Cloud and I have a repository but I am looking on how to automate our Merge workflow when using cloud:

- How Can I lock the Main Branch so code can only merged after review

- How Can we automate test based on some kind of label (The site mentions mergebots but this does not seem a solution on cloud).

- How Can we automate delivery, do you have a preferred Ci/CD provider that integrates well with Plastic.

 

We are using Unity but would not like to use Unity Cloud Build as it is a bit slow based on our experience but we are open to use it.

[Héber]

Hi Joseph,

 

I think what you are looking for, regarding all of your questions, are triggers: https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide. You could have a before-merge trigger that checks if the branch has an approved code review . If it doesn't, the merge will fail.

But, keep in mind that, for now, Cloud edition only works with webtriggers.

Regarding the CI system, we are compatible with a lot of them, like bamboo or teamcity, but we usually recommend Jenkins as we know it works well and is open source.

 

Best,

Héber..

[Joseph]

I think the cloud version features are still very immature to compete with github/gitlab/bitbucket. Currently it has little to no advantage of using Unity Collab unless we have a local repo.

[Héber]

Hi Joseph,

I'm sorry Plastic is not convincing you and that in your set-up it doesn't provide any advantage over collab.

That being said, we recommend you have a look at the task per branch workflow as it could be something worthy. Keep in mind that PlasticSCM allows for branching and creating code reviews for those branches, the usage of Gluon and partial workspaces, or the usage of local repos in case they are needed, for example.

If there is anything else we can help you with, let us know.

 

Best,

Héber.