is that a known problem?
after uninstalling it seems that a wrapper is still active since it is spamming this message when building:
"warning : Stashed service is not available. This will not be accelerated. Is the service running?"
"warning : Stashed service is not available. This will not be accelerated. Is the service running?"
In Logs, I get this Error: 2019/02/17 13:23:51.054 ERROR
Disable(): Object {reason: "msvs:v2017:211b1ebd:14.16.27023:x86_x64:remove d:\programs\microsoft visual studio\2017\community\VC\Tools\MSVC\14.16.27023\bin\HostX86\x64\cl.exe: Access is denied."}
reason: "msvs:v2017:211b1ebd:14.16.27023:x86_x64:remove d:\programs\microsoft visual studio\2017\community\VC\Tools\MSVC\14.16.27023\bin\HostX86\x64\cl.exe: Access is denied."
I want to demonstrate the advantages of this solution + incredibuild comparing times with or without stashed.io. What I'm doing is rebuild the project and taking times.
But I don't know how to enable/disable
Can someone help me figure that out ?
BTW I had the whole thing installed before any mention of licencing was encountered. I had thought it was free. Still, if it works well enough I can ask my company to pay and hope for the best!
I think they still let you pay for it though :/
I uninstalled it and am looking into just using ccache instead.
@janwilmans a lot of commits have been merged to ccache lately to support Windows and MSVC. Someone also releases binaries on github. I've not managed to get it to work yet mind you. stashed.io was cool though, except for the bug I hit which ended up costing more than the hours it saved me up til then!
Hey! I'm evaluating this staff for a dev team to get approval for license funds. Could someone please help me? Question is - what are the prerequisites for connecting agents from separate PCs in the same network? These are in the same subnet, connected by LAN, but don't see each other. Do I need to drop some settings in firewalls or anywhere?
Also a question - what is the strategy for renewing cache? Does it drop old-aged objects, or just not accepting new ones, or what? Our code gets global change once a month, so all previous cache becomes invalid. How to deal with that?
Should be back to normal. Many supporting cloud services by Google were removed and had to be re-written from scratch. Ahead of the migration, the old services still seemed to work just fine in the google cloud test environments. When the migrated code was deployed in production, the runtime blew up on the launch pad (still built and deployed correctly).
Heya Justin. What i mean is let's say i have built a project that lives in c:\foo. Now i rename foo to bar, so now it's c:\bar. When i build that project, will it be able to make use of the cache from when it was c:\foo\ or will stashed.io not be able to make that connection, so essentially has an empty cache for the project.
If the cache is based on a file content's hash, it would find it. If it's based on file path and timestamp, it would not find it.
We are using gitlab as a build CI/CD system and using cmake for our cpp application..
We just installed stashed in our build runner and triggered one pipeline post that job completion we can't see any stats in our local dashboard..Is there any configuration do we need to do
@thiyagsdevops I would reconsider that, potentially. You'll see from the chat it's hard to get much support; there's hardly anything going on. Hell we looked into it at my last job and couldn't get any responses; seemed dead/cancelled or at least hard to get going. Changelog not touched in 2 years, the issues on the repo linked to this chat are hidden now, etc.