1 pointThis is the same behavior using Xlinks or not. The "cloaked.conf" rules are applied only if the file is already in the workspace before you run the update. If the "cloaked.conf" file is downloaded during the update from the repo, I'm afraid the rules won't be applied during the initial update (but they will do the next time because the "cloaked.conf" will be already in your workspace). Regards, Carlos.
1 pointHi, If I properly understand, C is the parent repo that has Xlinks pointing to repos A and B. I'm able to create some cloaking rules in the C repo applied to the Xlinked content. I can do it via GUI --> right-click --> Add to the cloaked list. Then, If I create a new clean workspace pointing to C and before updating, I copy my previous "cloaked.conf", these files are not downloaded to the workspace. Remember that these cloaking rules apply to Xlinked content. In summary, I'm not able to reproduce your issue. Are you using the Windows Plastic GUI? Could you attach some screenshots and your "cloaked.conf"? Regards, Carlos.
1 pointHi, we have been using Plastic Cloud + Jenkins + Unity up until a few months ago. Support staff may have better answers, but hopefully this will get you going: This is happening because Jenkins is by default not running as your local user, but under the Local System account. C:\WINDOWS\system32\config\systemprofile\appdata is the %APPDATA% folder for the Local System account. You can change which account is used when launching Jenkins if you want to. Change these settings by starting the "Services" function in Windows, locating the Jenkins entry in the long list, and editing its properties. Ideally you should create a separate account (probably named "Jenkins") and run the Jenkins service under that. The config file location will then be C:\Users\Jenkins\AppData\Local\plastic4\client.conf. You need to ensure that two files exist in the config dir: "cryptedservers.conf" and one "*.key" file. You can copy the cryptedservers.conf / *.key file pair from your local user's Plastic folder. It is also possible to create these files programmatically, but that's a fair bit more work. 1+ year ago there were no hooks available in Plastic Cloud. We configured Jenkins to poll with 2-minute intervals - that was good enough for our purposes. The syntax to do so is to give a schedule like "H/2 * * * *" in Jenkins. ---- You may also find these references useful: Automation scripts for setting up and deleting Jenkins build slaves, for a Plastic/Jenkins/Unity build system: https://github.com/falldamagestudio/JenkinsAutomation Performance profiling results for a Jenkins build system: https://blog.falldamagestudio.com/posts/performance-optimizing-a-small-build-system-for-unity/