Jump to content
Plastic SCM forums are now in Unity. Click here to open the new forum ×

Cloud Edition & GitLab & Discord

MattLT

By MattLT
in Integrations

 Share

Recommended Posts

MattLT Newbie

MattLT

Posted
Posted

Hello,

We are a small team game development on Unity and we are actually migrating from Collab to PlasticSCM. 

We are using Gitlab for issue tracking and Discord as our communication tool.

It seems complicated to integrate PlasticSCM Cloud Edition in our workflow. There is not webhook for Discord neither Plastic Gitlab integration.

 

Do we have to develop our own tools to link everything to PlasticSCM ? What's the good way to do it ?

Is it even possible to do it with the Cloud Edition..?

 

Best,

Matthis Le Texier

Link to comment
Share on other sites
calbzam Proficient

calbzam

Posted
Posted

Hi,

- Plastic includes their own code review system. We have our own plugins for the main CI: TeamCity, Jenkins, Bamboo...  and also we have plugins for JIRA and some other issue trackers:

https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide

- We also have s solution to integrate with slack (but not with Discord):

https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide

- We have multple customers that use GitServer feature so they can use all the plugins/integrations available for git also in Plastic:

https://www.plasticscm.com/gitserver 

Every Plastic SCM server can now serve repositories using the Git protocol (git and http supported).

This means that every Git client can push/pull to a Plastic SCM server directly.

Any tool in the Git ecosystem can now be directly used to connect to Plastic SCM using their native Git functionalities. Teams on Plastic can now benefit from all the DevOps, CI, and project management integrations developed for Git.

You can now directly connect the following examples with Plastic: JIRA, Bamboo, FishEye, CodeCollaborator and many more.

GitServer is the server side counterpart of GitSync (which allows every Plastic SCM client to push/pull to a git server) and closes the Git interoperability loop.

- The problem is GitServer is not currently supported in Plastic Cloud. In order to use it, you would need to use a Plastic on-premises server.

Best regards,

Carlos.

Link to comment
Share on other sites
MattLT Newbie

MattLT

Posted
  • Author
Posted

Hi calbzam,

Thanks for your response.

You posted the same link twice. I saw the SlackPlug but, I don't quite get it. There is no entry point for Plastic Cloud. It seems impossible to do webhooks or anything like this. 

I also checked the plastic triggers, but once again, we have no access to Plastic Cloud Server so any manipulation is undoable. 

Can we use triggers on Plastic Cloud ?

Am I wrong or can we access Plastic Cloud server in any way ?

 

Best

Link to comment
Share on other sites
calbzam Proficient

calbzam

Posted
Posted

Sorry, the slack link was:

http://blog.plasticscm.com/2015/01/integrating-plastic-scm-with-slack.html

At the moment, webhooks (or any trigger) are not available for Plastic Clodu but they wil be available very soon. We are working very hard our new cloud2 insfraestructure (most probably availñable in the following weeks).

For now, I'm afraid you will need to install an on-premises server to use triggers and the GitSerevr feature.

Regards,

Carlos.

Link to comment
Share on other sites
  • 3 months later...
  • 5 months later...
Meceka Newbie

Meceka

Posted
Posted

Hello, after the new version with Discord integration (9.0.16.5128) I tried it with the cloud.

https://www.plasticscm.com/download/releasenotes

This is the command I used

cm tr mk after-checkin NotifyTeam "webtrigger https://discord.com/api/webhooks/****" --server=organization@cloud

It successfully adds the trigger but my colleague tested checkin with non-distributed setup and it in Discord it didn't work.

I work distributed, and I tested the same code but with local;

cm tr mk after-checkin NotifyTeam "webtrigger https://discord.com/api/webhooks/****" --server=repository@local

This works. But because my colleague doesn't have a local server this only sends notification to the channel when I checkin to my cloned local server. And I don't get any notifications when he checks in to cloud, or when I synchronise with cloud.

Is Discord integration not yet supported with cloud? Or am I doing something wrong?
 

Thanks,
Mehmet

Link to comment
Share on other sites
  • 2 months later...
xDavidLeon Newbie

xDavidLeon

Posted
Posted

Same issue.

I used: cm tr mk after-checkin NotifyTeam "webtrigger https://discord.com/api/webhooks/****" --server=organization@cloud

and this works for my checkins and for other users working directly on the cloud server, but it's not working for users that use the Sync to Cloud workflow.

I also tried adding 

cm tr mk after-checkin NotifyTeam "webtrigger https://discord.com/api/webhooks/****" --server=repo@local

with no success.

Also tried with 'after-clientcheckin'. Nothing.

Any help?

Link to comment
Share on other sites
xDavidLeon Newbie

xDavidLeon

Posted
Posted

Thank you Carlos.

Now each push event outputs "Replication write operation on myrepo", but no info about what the push operation contains (changesets comments?). Is there a way to add some info on these events? Right now, that message isn't really useful to check what has been pushed .

Cheers!

- David L

Link to comment
Share on other sites
calbzam Proficient

calbzam

Posted
Posted

Hi,

The trigger has some environment variables taht should useful, could you cehck in the triggers guide?

https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide#Serversidetriggers


before-replicationwrite
after-replicationwrite

Environment variables
In addition to the variables defined in sections Common environment variables and Server.conf variables, these are also available:

PLASTIC_BRANCH    

The complete branch specification which is being replicated. This is the format of the branch specification:
branch@rep:rep_name@server
The server member will be the destination server.

PLASTIC_REPLICATION_SOURCE    
Only available in the before-replicationwrite trigger.

The complete repository specification which is being replicated. This is the format of the repository specification:

rep:rep_name@server
The server member will be the source server.

PLASTIC_REPLICATION_ID    
Only available in the after-replicationwrite trigger.

The id of the replication.

Regards,

Carlos.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing
×
×
  • Create New...