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:

07:51:07.494    Using v2 root directory strategy         # this line is also new. is v2 broken maybe?
07:51:07.529    Success: Finished cloning repository files
07:51:08.384    No build output detected to cache. Skipping.
07:51:08.385    No dependencies detected to cache. Skipping.
07:51:08.483    Detected the following tools from environment: nodejs@18.17.1, ruby@3.0.6, npm@9.6.7
07:51:08.483    Installing ruby 3.0.6
07:51:08.895    To follow progress, use 'tail -f /tmp/ruby-build.20240111065108.378.log' or pass --verbose
07:51:08.966    Downloading openssl-1.1.1v.tar.gz...
07:51:09.220    -> https://dqw8nmjcqpjn7.cloudfront.net/d6697e2871e77238460402e9362d47d18382b15ef9f246aba6c7bd780d38a6b0
07:51:09.944    Installing openssl-1.1.1v...
07:52:21.076    Installed openssl-1.1.1v to /opt/buildhome/.asdf/installs/ruby/3.0.6
07:52:21.076    
07:52:21.081    Downloading ruby-3.0.6.tar.gz...
07:52:21.081    -> https://cache.ruby-lang.org/pub/ruby/3.0/ruby-3.0.6.tar.gz
07:52:23.061    Installing ruby-3.0.6...
07:56:19.605    Installed ruby-3.0.6 to /opt/buildhome/.asdf/installs/ruby/3.0.6


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
Was this page helpful?