How are global config changes propagated to the CLI client?

Hey there,

We’re using the plastic-global-config repo to add some config files & validation scripts to our different repositories; e.g., I might create a file named plastic-global-config/MyRepo/ignore.conf to have a default ignore.conf file in everyone’s MyRepo workspace.

However, for that to work, after I checkin the new ignore.conf file, everyone has to restart their UVCS clients in order receive that change (in their %HOME%/AppData/Local/plastic4/globalconfig/server/MyRepo/ folder).

Out of curiosity, how would that work for a user who only uses the UVCS CLI? How can they ensure that their local config folder has received the latest updates to the plastic-global-config repo? Is there a cm command they can run?

Running cm update on a related workspace should force the update of GlobalConfig.

Hope this helps!

1 Like