Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by calbzam

  1. calbzam

    Automating workflow with jira and mergebots

    Hi, would you mind reaching us at support@codicesoftware.com? We can arrange a gotomeeting session and help you with the setup. Regards, Carlos.
  2. calbzam

    Automating workflow with jira and mergebots

    Hi, Regarding the mergebot configuration, I guess you have followed the steps from: http://blog.plasticscm.com/2018/09/add-mergebot-to-your-repo.html Also, I guess you have filled all the "Issue Tracker Integration" values in the form and also created the plug. The mergebot is monitoring the branch attributes. For instance, once the branch has the attribute status=resolved, it will also check the status value in the JIRA task to check if it's ready to be merged. Regards, Carlos.
  3. calbzam

    Local Network replication (or proxy?) server with cloud

    You could host a local Plastic server (replicating to the cloud) to speed up your builds and your developers can still connect to the cloud if they prefer. Regards, Carlos.
  4. calbzam

    GUI 2D branch explorer

    Hi, I'm afraid the "2D revision history" view is not available. Just the regular "View history" panel. Regards, Carlos
  5. calbzam

    Add/set comment on branch using cm

    Yes, I recommend you to upgrade to get the latest features
  6. calbzam

    Add/set comment on branch using cm

    Hi, you can change the changeset comments via: cm changeset editcomment More info at cm changeset --help But I'm afraid you cannot change the branch comment via command line. Regards, Carlos.
  7. calbzam

    Local Network replication (or proxy?) server with cloud

    Hi, I think we already answer your support ticket. Just to summarize: - Plastic Cloud doesn't support a proxy server. Note that the proxy server is just a data cache server, not a full hosted server allowinh replicas... - You can always host your Plastic server and your developers connect to it instead of the cloud. This way, you can also use the locking workflow. - You can still use the cloud to replicate your repos from your hosted server (or to support the workflow for distributed people) but note that the lock workflow will only work if all the developers are pointing to the same central server (hosted or cloud). Regards, Carlos.
  8. calbzam

    Apply windows folder/file locks to a read-only xlink

    Hi, Plastic can prevent to checkin the changes to a read-only Xlink but it can't prevent an external tool to locally modify these changes out of the Plastic control (eg. via Windows Explorer or text editor). I think you asking for something at the OS level? By the way, Plastic support creating triggers for specific repos. https://www.plasticscm.com/documentation/triggers/plastic-scm-version-control-triggers-guide eg: cm mktrigger before-mklabel "label-bl-fix" "c:\tmp\triggers\label-bl-fix.bat" --filter="rep:default,bl*,fix*" Regards, Carlos.
  9. calbzam

    "replicate" one server to "another"

    You can try to enable gitserver and check if this way you can workaround the problem. For the replica error you reported, it seems to be a database problem (the guid ... for the object was not found). Why don't you just upgrade your original Palstic server to the last 8.0 version and try to migrate to git from this new version (it includes improvements in gitsync and gitserver). We can follow the different approaches to migrate to git, but I would do it from the last Plastic version. Also, what is your company name and registered account at www.plasticsc.com? Regards, Carlos.
  10. calbzam

    "replicate" one server to "another"

    Hi, If you reach us at support@codicesoftware.com we can arrange a meeting to review your setup. The problem may be network related (not sure if it always fail at the same point). Also, If you are trying to migrate the repos, you can also follow a different approach: migrate your repos to Jet and just copy the databases to the new server. Regards, Carlos.
  11. calbzam

    Server upgrade 5.0 to 8.0

    Hi, The installer will perform the server upgrade for you (both server binaries and databases). You will also need to upgrade your clients to connect to the new server version. The only thing to consider is that Firebird databases are not very recommended for production in a central server. We recommend you to migrate the databases to Jet (our file-based database system). You will get better performance. https://www.plasticscm.com/documentation/administration/plastic-scm-version-control-administrator-guide#ConfigurePlasticSCMwithJet Also, if you are using an unlimited license, you will need to reach us at support@codicesftware.com in order to generate anew license with Plastic 8.0 support. Regards, Carlos.
  12. calbzam

    Arrow directions flag in config files

    I'm pretty sure the option 2 is not configurable. Anyway, let's wait for him to answer. it should be possible to render the branch explorer like option 1 by setting the flag. Regards, Carlos.
  13. calbzam

    Phantom file changes

    Hi, If the files are downloaded during a merge, there should be somehow involved in the merge conflicts. Are you using "cloaked.conf" rules? If some cloaked files are involved in the merge, they will be appearing in the workspace after the merge. I guess you are using the Plastic GUI (not Gluon)? Regards, Carlos.
  14. calbzam

    name_conflict files added during merge

    Hi, This "name_conflict" files appear when a merge operation needs to download a specific file but it already exists in your workspace. It could happen for instance if you already had a private file with the same name on this path. Do you have "cloaked.conf" rules? There are also some scenarios it could also happen with cloaked files. Regards, Carlos.
  15. calbzam

    Updated plastic:// URLs to launch diff windows

    Well, you are right that this feature is probably not very well documented. You should be able to use both changeset id or guid. Regards, Carlos.
  16. Thanks for the update!
  17. Hi Marc, From the Plastic GUI --> Preferences, you can configure the external merge tools (eg: UnityYAMLMerge). Plastic just try open the external merge tool based on the configured parameters. You need to be sure the external tool path and required parameters are correct. I've found this Unity guide where they explain how to configure UnityYAMLMerge with third party tools (like Plastic SCM): https://docs.unity3d.com/Manual/SmartMerge.html Regards, Carlos.
  18. Hi, If you attach the server debug log, we can check if the web admin is actually running or not. Anyway, we can also configure the server via "clconfigureserver" tool or editing the configuration files so we can also help you to configure the server not using the web admin. Regards, Carlos.
  19. calbzam

    Arrow directions flag in config files

    Hi, Göran proposed to align the arrows with the direction of time while Pablo is following a different approach: https://plasticscm.com/book/index.html#_arrow_direction The option you mention should apply only to the merge links but not for tot he changeset links. Regards, Carlos.
  20. calbzam

    "replicate" one server to "another"

    Could you attach the "plastic.debug.log.txt" file? This error could be network related. Is it failing always at the same point? If you are trying to migrate the repos, you can also follow a different approach: migrate your repos to Jet and just copy the databases to the new server. Regards, Carlos.
  21. calbzam

    Will Plastic 18.0.16 sync with a 17.0.16 server?

    Hi Tom, Both versions are fully compatible. No problem running a sync between them. The third number in the version number represents the compatibility. Regards, Carlos.
  22. Hi, What is your Linux distro? Are you facing an installation issue or you cannot connect to the server? Regards, Carlos.
  23. Hi, If I properly understand, you are trying to apply a similar workflow you are currently using with ClearCase into Plastic SCM. Let me show firstyou the following link where we show some reasons to consider Plastic instead of CC http://blog.plasticscm.com/2012/05/want-to-switch-from-clearcase-this-is.html In my opinion, it would make more sense to adapt your previous workflow to get the best experience with Plastic SCM. Instead of trying to replicate exactly the same procedure you are currently using with CC. If you reach us at support@codicesoftware.com, we can arrange a session and discuss the details. Answering your question: - In Plastic SCM the basic element is the changeset and a long time ago we switched from a per-file merge tracking to a per-changeset merge tracking. Key differences between per-file and per-changeset: (http://blog.plasticscm.com/2018/02/why-checkin-asks-to-update-first.html) Speed: if you merge 1000 files, per-file will need to walk 1000 version trees, one for each file. It doesn't scale. That's why old version control systems normally prevented developers from using too many branches. Merge all or nothing: with per-changeset when I merge a branch I merge all the files changed on the file... or none, but I can't simply merge a few. This is because the link is set per-changeset, so there's no way to say "hey, only a few were merged, keep the rest for a future merge". With per-file you can do that. When you merge task127 to main you can decide to merge only foo.c, and bar.c will be proposed again to merge if you try to merge the branch again. Flexibility comes at a cost - performance and much higher complexity. - Following this same philosophy, a Plastic label is applied to a specific changeset (not to a file). So if you update your workspace to a specific label, you will actually download the full content of the labeled changeset. - If you still want to follow a file-based workflow, Plastic also has too called Gluon. It comes with Plastic, has no extra cost, and supports a different workflow. It is perfect for working with non-mergeable files (art, docs...). - In Plastic, every operation can also be achieved via command line "cm". The "cm cat --help" command allows downloading the content of a given revision. If you want to update your workspace to a specific label, you can run " cm switchtobranch --label=BL050". Regards, Carlos.
  24. calbzam

    Cannot Checkin large repository

    Hi, - Regarding the auto-refresh. You can enable it (as David explained). It's not enabled by default because with big workspaces or slow disks it could take very long to calculate the pending changes. - We also offer a free 1-hour training session for new companies so can request it if some workflows/features are not clear enough. Thanks for your feedback! Carlos.
  25. calbzam

    Plastic code review on Linux

    Hi, the Linux GUI doesn't have integrated code review support. But we released a few months our new webUI including support for a multiplatform code review. You may want to give it a try: http://blog.plasticscm.com/2018/09/webui-web-interface-for-plastic.html Regards, Carlos.