Héber

Hi Thomas, Did you recently add a some items to a cloaked list? I'm afraid they are not compatible with the update-merge workflow. Did you have enabled the "Run fast update" option? Best, Héber.

Hey! Thank you very much! This is a wondreful surprise We will keep pushing forward to create a strong and solid VCS. Best, Héber.

Hi Wolfram, Yes, you are right. The order doesn't affect at all. How do you feel about it? Would you prefer it to work having the order in mind? Just be aware that *~ is a name rule, if you use it, you can't deny rules inside the path of folders that ends with the ~symbol. I'd say that it is not going to work when you want to deny things inside the Samples~ folder. Best regards, Héber.

Hi Wolfram, That's quite a special setup you have there! I'll try to explain how to do it as best as I can, and provide you with the rules I think will let you have the ignore list as you wanted. Your solution was not working because the recursivity you were using applied only to the path rules, leaving out name rules. This is a difference between our ignore.conf and gitignore. First of all, you will need the /**~ rule. You need this instead of /*~ because this one ignores directories, but not the contents inside of it. Then, you add the following ones: !^/[^Ll].*/Samples~$ !^/[^Ll].*/Samples~/.*[^~]$ !^/[^Ll].*/Documentation~$ !^/[^Ll].*/Documentation~/.*[^~]$ These rules unmatch Samples~ and Documentation~ directories and its contents, unless the path starts with "L" or "l", so you ignore the ones in Library. After unmatching those rules, we want to ignore the whole Library folder, so we add a rule for it: /Library So, the whole file should be something like this: /**~ !^/[^Ll].*/Samples~$ !^/[^Ll].*/Samples~/.*[^~]$ !^/[^Ll].*/Documentation~$ !^/[^Ll].*/Documentation~/.*[^~]$ /Library Just for your information, note that this will work: /src !/src/foo /src/foo/bar But this will not: src !foo bar It is due to the name vs path recursivity I said above. Hope this helps you, and feel free to ask anything you need. Best regards, Héber.

Hi Mehmet, Yes, you can set your local server to use encryption on the server side. You would need to add the cryptedservers.conf file to your server folder under "C:\Program Files\PlasticSCM5\server" and the key. Then, you would have to share that key with all the machines you want to grant access to the repo. It is added in the client folder, where all the client configuration files are, under "C:\Users\YOUR_USER\AppData\Local\plastic4". You can check the following link to see how to do it: http://blog.plasticscm.com/2015/02/how-to-setup-encrypted-server.html Just be aware that you probably have to set local instead of localhost as the server name in the cyptedservers.conf, as it is how the local server created with cloud edition is named. For example, change: EncryptServerIP:8087 carlosLocal.key To: local:8087 mehmetkey.key Best regards, Héber.

Hi again! I just wanted to point out that, although we don't have a proper integration, a custom one can be made. check the following documentation if you are interested https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide#WritingPlasticSCMcustomextensions Best regards, Héber.

Hi, I'll share it with the team. Thanks! Let us know if you need anything else. Best regards, Héber.

Hi Jani, I'm afraid Code Review replication is not supported, so it won't be fully functional in your setup. But, don't panic, as there are some options. First, to send the metadata without needing to create a new changeset, you can right-click on the branch, then "push/pull" and then push the branch. This way, all the metadata should be sent. The other option is to work directly against cloud, but it is not what you want. You can still perform code reviews, however, you won't be able to change the status when checkin in, you won't be able to see the comments GUID. I think this stands for questions a and c. For question b, you can create a code review directly to cloud without needing to create a new workspace. Just go to the repositories view, right click the desired repo, view branches, and then new code review for the desired branch. As I have said, this way you can create code reviews, but replication is still not supported, so you will be able to get it, but not to submit the status change directly. Tell me if I haven't been clear, or if there is anything else I can help you with. Best regards, Héber.

Hi, Yes, adding those files to the cloaked list would prevent your team from downloading them. However, the cloaked.conf should be in their own workspaces so you would have to share it with them. Best regards, Héber.

Hi Silas, I'm afraid right now importing LFS files is not supported. The best way to have them is to perform a fast-import to get the history of the repo, and then manually copy the files into the workspaces. After that, you just push the changes and you have the repo up to date. But I'm afraid you won't have those LFS files old revisions. Best regards, Héber.

Hi Marc, I'm afraid we don't have anything official, but you can check this thread: You will need to install mono and then proceed with the zips provided. We know other users have installed it in their Synology NAS, but it is not officially supported. Best regards, Héber.

Hi! Would you mind sharing the terms you used in your search? We want to improve it and see why you couldn't find any proper information. Best, Héber.

Hi, Glad you could do it! Subtractive interval was the best option there, yes. Other option was to delete the changests if you didn't want to keep the history, but we do not recommend it. I'll share it with the team, because if it was hard to find for you, it will probably be hard for the rest of our users. Best regards and thank you for the feedback, Héber.

Hi Francois, Which is your client version? It should disappear if you upgrade to the latest one. If it doesn't, could send the plastic.debug.log.txt to our support e-mail support@codicesoftware.com please? Best, Héber.

Hi Emran, Could you please send us both this message and the client plastic.debug.log.txt to support@codicesoftware.com ? It is a bit weird and we need to review those logs to see what is preventing Plastic GUI from launching. Best, Héber.

Hi, We found the problem: there is a bug in the transaction code that is causing a deadlock. It is caused by a very, very strange condition. We suspect the bug has been there sitting for months. We'll do our best to fix it asap.What we've done already is to sequentially restart the nodes attending requests, so the service will get back to normal.Everything should be working by now. Sorry for the inconveniences, Héber.

Hi, I'm afraid you are right. Changing the font on Mac is something not implemented. I can add it as a feature request if you want. Best, Héber.

Hi, I'm afraid that option is not a Plastic one, but a Mac native one. We can remove the option from the menu, but it is what MacOS provides by default. Regards, Héber.

HI, I'm afraid not. Semantic is no longer available for Linux. We will post it if it is available in the future. Sorry for the inconveniences. Best regards, Héber.

Hi, We have the following documentation about how to get Plastic working with Jira: https://www.plasticscm.com/documentation/extensions/plastic-scm-version-control-task-and-issue-tracking-guide#JIRAintegration So, you can't get your task set as done after adding the attribute in Plastic? Does other state transitions work for you?. Please send us the following information in order to check it: The repo you are working in. (If it is a local one, against cloud, on premise... ) The branch prefix and the proyect key The plastic.debug.log.txt in the logs folder. Best, Héber.

Hi Wolfram, You can set the branch explorer date filter to a given year and it will remain in that year for every repository you open. Even if you close the GUI. You shouldn't need to do it for every repository. Best, Héber.

Hi, Are you using plastic cloud? Can you send me the next info? The repo you are working in. (If it is a local one, against cloud, on premise... ) The branch prefix and the proyect key The plastic.debug.log.txt in the logs folder. We will check what could be happening to you and contat you ASAP. Best, Héber.

Hi Andy, Right now, a bot is the only way. This post should help you to create and integrate one with slack: http://blog.plasticscm.com/2015/01/integrating-plastic-scm-with-slack.html Hope this helps. Héber.