Héber

Hi, We are handling this via e-mail. We will update this thread once we have the solution. Best, Héber.

Hi Matt, Yes, it is free. Don't worry about that message as it is a visual issue only. Once those days have ended, you will be able to keep working without any problems. Best, Héber.

Hi, Once you have your cloud organization up and running you can just create a new sync view for the repo you want to move to a new repo on the cloud server and run it. That would get you an exact copy of your local repo up there and you will be able to use it without issues. Then you have two options. Either you work distributed pushing your changes to the cloud, or you work centralized with the workspace pointing directly to the cloud server. I think it's easier the second one, but depending on your connection it might take you some time. You could also work only locally. Best, Héber.

Hi Jeff, I'm sorry for the late reply. As you said, we don't encourage the modification of the history because it can lead to this kind of scenarios. The only way to fix it without having to create a new local repo is to have another teammate create a new changeset where the deleted one was supposed to be, as you did. I'm sorry for the inconvenience. Best, Héber.

Hi, I'm afraid there is no way to do it right now. We are working on a trimming tool to reduce the space that it takes, bt right now it is not possible. Another option I can think of, if you don't need all the branches for example, you could replicate to a new repo only the main branch and the ones you are currently using and then delete the previous repo. This is not an optimal option, but it might help you save some space. I'm sorry for the inconvenience. Best, Héber.

Hi Wolfram, I'm really sorry for the late reply. I will try to reproduce the issue as soon as I can and share it with the team to see what can be done. Thank you for the report! Best, Héber.

Hi John, Are you using a WiFi connection? We have seen this error in the past and it comes due to some network issues. Probably using a different network or a wired connection will let you perform the whole checkin. That's why you were able to submit them one by one. Best, Héber.

Hi, I think it is more of a configuration issue. Anyway, could you reach us out at support@codicesoftware.com to schedule a meeting and review it together? You can ask for myself (Héber) as I think it will be easier that way. We can then update the thread. Best, Héber.

Hi, If I understood you properly, you just need one installation, the on premise one in this scenario. With it you should be able to have your local server related to the enterprise edition and get connected to it with no issue. Once you have a cloud organization, you can access everything from the same client just by selecting the cloud server: In this screenshot, you can see an on premise client working against a cloud organization. I have a central server I access with this client, a localhost one for personal projects and distributed workflow, and a cloud one. You can still create sync views between them or work centralized against any of them. In the following GIF you can see how I have access to those three repos: Does this help you? Is it clear now? Best, Héber.

Hi Wolfram, I'm sorry for the delayed answer. I'm afraid it doesn't work that way either. It is going to show you the same timespan you have selected in the branch explorer view. So if you select a file that was not modify in that timespan, it is not going to show you any data. But it keeps the one from the branch explorer. Which behaviour would you like to have? To allow you to specify a determined query and have it for all the repos? Or maybe an option like the one in the branch explorer? All the feedback is welcome, as you can be thinking of an option we weren't even considering. Best, Héber.

Hi Andy, No, Plastic doesn't install Ruby, but it was given as an example. You can use the same trigger in the language that better suits you. For example, a lot of users use Python. That would be an option too. Server-side triggers do work for checkin operations, so it should be fine. Let me know how it goes or if you need asistance with it. Best, Héber.

Hi Josh, I have just tested it in a Ubuntu 19.10 and it worked fine. Let me explain you what I did on a fresh install: Went to "/etc/apt/sources.list.d". Created file "bionic-oldlibs.list". Pasted into that file these two lines: deb http://us.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://us.archive.ubuntu.com/ubuntu/ bionic universe Performed a "sudo apt ugrade". Follow the instructions to install Plastic in Ubuntu as written in the following link: https://www.plasticscm.com/plastic-for-linux Installed the cloud edition. Rub "gtkplastic". That led me to a working installation of Plastic cloud edition (you can check it in the attached image). Is there any reason in particular why you wanted the cloud client? Best, Héber.

Hi Joe, Are you pulling it from a cloud server? The problem is that while you are trying to access those files to pull them, there is another process locking them, maybe a database transaction. Depending on the destiny of the pull, there are different things to do. So lets keep going with this issue step y step. Best, Héber.

Hi Toni, Short answer: Yes, but... Long answer: Since Ubuntu 19.10, one of the libraries we use for the GUI has been removed from their repos, so it is not possible to run it. You can still use the command line client and the server, but no GUI is available. However, that missing library can still be downloaded from Ubuntu bionic repos, so adding those repos to the apt tool. To do so, you need to create the "bionic-oldlibs.list" file under "/etc/apt/sources.list.d". Inside that file paste these two lines: deb http://us.archive.ubuntu.com/ubuntu/ bionic main restricted deb http://us.archive.ubuntu.com/ubuntu/ bionic universe These are the latests long term repos with the missing library. If you now perform an "apt update" and try to install Plastic again, you should be able to do it without issue. Best, Héber.

Hi Andy, I'm afraid there is no option to make sure a checkin has a comment by default, but you could create a before checkin trigger that ensures there is one. You have an example that does that exactly here: https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide Best regards, Héber.

Hi Tyler, I have been working on this and trying to get it working as you are doing, but so far I haven't been able to set the changeset to build, as it only allows me to add a branch. You can check it in the attached image. Can you tell me where are you adding it? Furhtermore, we released a task some time ago where the behaeviour of the "update" was changed. [New] All platforms – Plastic, Gluon, command line: Now update always goes to latest. Suppose you switched your workspace to a particular changeset, then decided to update. You were stuck on that changeset, by design. We thought (for a few years already) that if you had switched to a given changeset, why would you want to jump to latest during an update? But then we realized it was a true UX pain. Why wouldn't you want to switch to latest? So, we just changed the behaviour. Now, when you update, you'll always go to latest in the branch, even if you were working on a given changeset or label before. It was done the 2019-07-23, and released on version 3470. Were you using a previous version when it was working? Best, Héber.

Hi Tyler, We have been going through the issue, but we were not able to reproduce it yet. We are still trying some scenarios, but anything you could tell us about your setup would help. Best, Héber.

Hi Jani, Can you send us an email to support@codicesoftware.com with the information and attach the client plastic.debug.log.txt file? Best, Héber.

Hi, You can still perform it from the regular GUI going to the branch explorer and right clicking there a branch, then Push/Pull and finally sync with git. I know it is more tedious and definitely not a comfortable option for Gluon users, but I'm afraid it is what we have now. I'm sorry. Best, Héber.

Hi, I'm afraid gitsync is not supported in gluon. You can perform it from the regular Plastic GUI, but not from Gluon. I'll share it with the team, but for now it is not available. Best, Héber.

Hi, I'm glad you have it working! It would probably need everything to be updated and took it some time. Best, Héber.

Hi Mark, I'm afraid Code Review replication is not fully supported yet for distributed workflows. In order to have the metadata changes pushed to cloud you need to have a new changeset. You can also push/pull the branches without a syncview, and most of the metadata will be pushed with it. You can also create a centralized workspace to perform code reviews changes, as a workaround until replication is available. I understand this is not a great option, but it might solve your issues for the moment. Notice that you would have sort of a "dummy" changeset with just a code review. Best, Héber.

Hi, I'd say there is an error in the connection settings. Can you please write an e-mail to support@codicesoftware.com with the details of the issue and attach the server plastic.debug.log.txt ? Best, Héber.

Hi Wolfram, Thanks for the feedback. We will have it in mind. However, as you said, changing it right now would annoy the rest of the users. In that case, forget what I said. Glad to hear you have it working as you wanted it. Best regards, Héber.

Hi! That's great! Of course you can use the logo. We can provide you with a different one as well if you want, just say it out loud Would you be interested in making a blog post about it? Best, Héber.