Trond Posted January 20 Report Share Posted January 20 Hello, Some time ago I got a tip on this forum to look into CmdRunner to improve performance for custom tool integrations. I am currently testing out https://github.com/PlasticSCM/plastic-cmdrunner , and while it seems to have better performance, I have some worries it would be nice to have cleared up: The repo hasn't had any updates for 5 years. Is it still actively maintained? There are a couple of long-standing unresolved issues, particularly this one (I'm not usually working on Windows so it's a bit cumbersome to test given that there's no specific repro-steps I realize there are kind of repro steps by re-reading the issue again), which I'm not sure if is still a problem, or if the suggested fix is causing any unexpected side-effects: https://github.com/PlasticSCM/plastic-cmdrunner/issues/1 While Mac is our main development platform, some of our team members occasionally work on Windows, so I'm not sure how likely we are to get affected by this. There's no license attached to the repo, so I'm a bit hesitant to use it for production (I filed an issue about this). Edit: FWIW I would very much prefer the CLI tools to be fast enough to not need this kind of wrapping. Are there any plans on looking into this? The conclusion from this thread was that it's caused by application launch overhead: https://forum.plasticscm.com/topic/23494-cli-tools-slow/#comment-46676 Using the CLI tools manually works okay-ish, but it's incredibly much slower than say Git just to get the current workspace status. Best, -Trond Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now