GardensSiobhan

Any updates on Cloud + GitServer support?

What's the current state of Crucible integration with Plastic Cloud? I downloaded the Crucible plugin and followed the extremely limited instructions in its README. The plugin shows up in the list of add-ons and can be configured (following the walkthrough at https://www.youtube.com/watch?v=-ocQTtwRJxc as far as I could), but Plastic doesn't show up as a valid repository type in Crucible afterwards. Does the Crucible plugin work with Plastic Cloud?

I'm trying to create a CodeCollaborator review of a changeset using the instructions found here: https://www.plasticscm.com/documentation/technical-articles/codecollaborator-send-plastic-differences. I get the error message "Unable to send differences to CodeCollaborator: GetChangesetsInfo(RepId repId, List<long> csNumbers) is not called from the client. Implemented due to interface restrictions." 1) Pretty obviously, the actual error is the "GetChangesetsInfo()..." part. Is that being returned from the CodeCollaborator API, or from the Plastic API? 2) Is codecollaboratorclient.exe supported when using Plastic Cloud?

For anyone finding this question in search later: The answer is that the URL can be found in %LOCALAPPDATA%\plastic4\cloudregions.conf. Only grab the hostname from that file; the port number will be the API's standard 7178.

The client REST API documentation states that it cannot manage attributes. However, the Swagger file for the server REST API, which as a Cloud user is what's relevant to me, has a definition for ChangeAttributeRequest that seems like it would at least allow setting (though not getting?) attributes with server REST calls. Unfortunately, the Swagger file doesn't give an endpoint path for ChangeAttributeRequest. What is the actual status of attribute support in the server REST API?

Aha, thanks Fury22, that helped. Formalizing this for anyone reading in the future: If a webhook returns an HTTP status code other than 200, the trigger will fail, and the body of the HTTP response will be reported to the client verbatim. cm attribute create FOO The trigger before-mkatt [before-mkatt] failed. arglebargle.

My organization has a Cloud repo, and I'm trying to use the server REST API. The documentation says "If you'd like to access the API from the cloud, you need to know the base URI of the server that hosts your organization." Where can I find that value? Is it related to the PLASTIC_SERVER value I see in the logs of my webhooks?

Yes, I have this same problem. I'm using Cloud, and would like to create a before-mkbranch webhook that will refuse the creation of a branch when criteria aren't met. The docs say that a non-zero output result will block creation, but they don't say what "output result" means in the context of a webhook. Does Plastic parse the body of the webhook response?

Is this still an issue? I'm having this same basic problem and am trying to understand whether it's on Plastic's side or mine.