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

manu

Administrators
 View Profile  See their activity

  • Posts

    4,599

  • Joined

  • Last visited

  • Days Won

    130

 Content Type 

Posts posted by manu

  8. Cross-platform Client-side triggers

    in General

    Posted

    It good to hear that the "....rigger after-update "after update" "ruby /foo/bar.rb"" trick worked! :)

    That seems to work for us. It's actually kind of nice in that we don't have to configure this trigger for each machine.

    Yes but I think it can be confusing since you can think that it's only a local client trigger.... I have added a task into our bug tracking system in order to allow both behaviors.

  11. Cross-platform Client-side triggers

    in General

    Posted

    Hello Logan,

    the update triggers are client side triggers, they are executed in the client machine.

    The MAcOS "/Users/...." path is not valid for a Windows machine so you need to install ruby in the windows machine and create an update trigger in the windows machine.

    In this way the MacOs machine will run the MacOS trigger and the Windows machine the Windows trigger.

    Are you using shared workspaces?

  16. 4.0 Exclusive checkout - not seen on other clients

    in General

    Posted

    Hello andsee,

    I think the 4.1 with the exclusive checkout feature will be released this week. I'll shortly explain you how it works. The exclusive checkout (locking) can now be configured per path.

    To configure it create a file "lock.conf" in the server directory

    with the following format:

    rep:local_repname lockserver:server:port

    path_rules

    where

    * local_repname: is the name of the repository where you want

    to perform exclusive checkouts

    * server: the lock server

    * port: the port where the lock server is configured

    * path_rules: an entry per rule specifiying file names

    with wildcards

    Example:

    rep:default lockserver:localhost:8084

    *.doc

    *.xls

    *.jpg

    document.vcs

    /install/readme/*

    Once the file "lock.conf" has been created and the server restarted,

    each time a file matching the rules is checkedout, it will be checkedout

    in exclusive mode (locked), so no other checkout can happen.

  17. Renaming repository leaves dangling workspaces

    in Community Edition

    Posted

    Hi, you are right, it's not a very clear operation right now. We are working to create a smoothly mechanism to achieve a successful rename.

    In most of the case you don't need to delete your workspace, just close the GUI, open a command line window, cd to your workspace path and run a "cm update ." command. If this is not productive you can delete your "C:\..\wkPath\.plastic\plastic.wktree" and repeat the update.

  21. Is there an easy way to determine the version/build of Plastic SCM?

    in General

    Posted

    Hello Tom,

    for the client is quite easy: "cm version".

    For the server it's a little bit tricky, but you have two options:

    First:

    • Stop the windows PlasticSCM server service.
    • Open a command line window, change the dir to the PlasticSCM server directory.
    • Issue the following: "plasticd.exe --console" it will prompt you something like this:

    
Creating ServerSink
Plastic SCM daemon up. 4.0.236.0 3650 ms startup time

    Second:

    • Open the "loader.log.txt"/plastic.log.txt file on the PlasticSCM server and search for something starting with: "INFO Daemon - Plastic SCM daemon up "
    • Get the last entry.

    Manu

×
×
  • Create New...