Cache broken?
Since January 11 the build time of our pages application has increased from 1.5m to >6.5m with (AFAIK) no changes in the setup on our side.
The build log now includes the following lines:
Looks like caching is broken. Did you change something on the setup on your end?
Please check and fix asap. Thanks!
- application: https://scrivito-ui.pages.dev/
- deployment ID: cb712e2a-33d4-45e7-9166-ba84023457f0 (and all subsequent deployments since then)
- account: bacbc29ade73964a4eb1e298f28629fe
5 Replies
Hey @Markus, I'm passing this internally for the team to check, it could be on Ruby's side but can't check that without logs, and also looks like we did an image release on that day so could be an issue on our side
@Vero 🐙 any update on this? When will this be fixed?
This is a major regression and we are actually quite surprised that a bug of this scope was not discovered by your internal QA.
Hi, this was escalated to the Pages team engineers, but isn't fixed yet
they are investigating the increased build times only, because they saw cache isn't actually broken
they are investigating the increased build times only, because they saw cache isn't actually broken@Vero 🐙 are you sure? then why do these lines show up in the logs suddenly?
07:51:08.384 No build output detected to cache. Skipping. 07:51:08.385 No dependencies detected to cache. Skipping.
not sure why those lines but the team checked internally and confirmed it isn't broken
They just told me that it looks like the time is spent installing Ruby, which unfortunately takes a while.
Did you add a
.ruby-version
file to your repo? If so, can you try removing it and see if it speeds up?
@Markus