You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bootstrapping took '00:00:00'
Reading configuration took '00:00:00.0003681'
Loading modules took '00:00:00.0004979'
Analyzing the script took '00:00:01.2996956'
Installing tools took '00:00:00.4002853'
Installing addins took '00:00:00.0942559'
Create session took '00:00:00.0005095'
Loading references took '00:00:00.4481680'
Loading aliases took '00:00:00.2436325'
Importing namespaces took '00:00:00.0009081'
@GeertvanHorrik just to make sure that I have understood this correctly...
Are you saying that you are using the build script cache, across different build agents? Which is why you are seeing the path to the scripts be different in each case? How are you keeping the build script cache "alive" between build executions? Are you using some sort of caching at the build agent level?
Just want to make sure that I am understanding the need for the change here.
No, not different build agents. Different builds, where the build agent assigns a different folder (unique to the build) every time. This is to introduce caching on the build agent level (or, for that matter, even on local builds since we use exactly the same scripts to do local nuget packags on dev machines).
Activity
GeertvanHorrik commentedon May 15, 2025
Added some more timings:
GeertvanHorrik commentedon May 15, 2025
I think I found a useful pointer why caching is not working. The contents contain full path names:
But... on (most) build agents, it will be a random, unique directory:
I think using simplified paths for script cache comparison could work here, doing some additional testing.
(cake-buildGH-4471) Improve script cache hash generation algorithm
gep13 commentedon May 20, 2025
@GeertvanHorrik just to make sure that I have understood this correctly...
Are you saying that you are using the build script cache, across different build agents? Which is why you are seeing the path to the scripts be different in each case? How are you keeping the build script cache "alive" between build executions? Are you using some sort of caching at the build agent level?
Just want to make sure that I am understanding the need for the change here.
GeertvanHorrik commentedon May 20, 2025
No, not different build agents. Different builds, where the build agent assigns a different folder (unique to the build) every time. This is to introduce caching on the build agent level (or, for that matter, even on local builds since we use exactly the same scripts to do local nuget packags on dev machines).
gep13 commentedon May 20, 2025
Gotcha! Thank you for the clarification, this helps!
(cake-buildGH-4471) Improve script cache hash generation algorithm
github-actions commentedon Oct 4, 2025
ð This issue has been resolved in version v5.1.0 ð
The release is available on:
Your GitReleaseManager bot ðĶð