Home → Problems →

Jobs began to say "Build cache is not configured for the build environment"

• Edit

jimklimov

06 Aug, 2025 11:38 PM

I am using the free Appveyor CI layer to test Windows builds of a FOSS project. Using cache of various directories used to help significantly, with one nit that a failed build (e.g. due to hitting the 1hr timeout) tends to lose the cache even if APPVEYOR_SAVE_CACHE_ON_ERROR: true is set.

Now I am trying to get it re-initialized, however even with shortened runs (without tests etc.) the job succeeds overall, but states that "Build cache is not configured for the build environment" both when starting the job (where it should unpack existing data) and when ending it.

For example, see a recent https://ci.appveyor.com/project/nut-travis/nut/builds/52524804?full... with such fault both on start (sort of expected even if annoying) and at the end of job (unexpected, this part of the appveyor.yml recipe did not change):

Build started
git clone -q --branch=master https://github.com/networkupstools/nut.git C:\projects\nut
git checkout -qf 4ea6a4e65332dce410e9ec7c21f3fb0cedf34880
Build cache is not configured for the build environment.
Running Install scripts
...
...
...
Discovering tests...OK
Collecting artifacts...
Found artifact 'config.log' matching 'config.log' path
Found artifact 'config.nut_report_feature.log' matching 'config.nut_report_feature.log' path
Uploading artifacts...
[1/2] config.log (1,710,584 bytes)...100%
[2/2] config.nut_report_feature.log (5,813 bytes)...100%
Build cache is not configured for the build environment.
Build success

An earlier successful build https://ci.appveyor.com/project/nut-travis/nut/builds/52497342?full... (ran a week ago) did have the caches:

...
git checkout -qf FETCH_HEAD
Restoring build cache
Cache 'C:\msys64\home\appveyor.ccache' - Restored
Cache 'C:\msys64\var\cache\pacman\pkg' - Restored
Cache 'C:\msys64\home\appveyor\nut-win-deps' - Restored
Running Install scripts
...
...
...
Collecting artifacts...
Found artifact 'config.log' matching 'config.log' path
Found artifact 'config.nut_report_feature.log' matching 'config.nut_report_feature.log' path
Found artifact 'NUT-for-Windows-x86_64-SNAPSHOT-2.8.3.3423-master.7z' matching 'NUT-for-Windows*.7z' path
Uploading artifacts...
[1/3] config.log (1,714,455 bytes)...100%
[2/3] config.nut_report_feature.log (5,872 bytes)...100%
[3/3] NUT-for-Windows-x86_64-SNAPSHOT-2.8.3.3423-master.7z (61,496,073 bytes)...100%
Updating build cache...
Cache 'C:\msys64\home\appveyor.ccache' - Updated
Cache entry not found: C:\msys64\home\appveyor\ccache
Cache entry not found: C:\Users\appveyor\AppData\Local\ccache
Cache entry not found: C:\Users\appveyor\AppData\Local.ccache
Cache 'C:\msys64\var\cache\pacman\pkg' - Up to date
Cache 'C:\msys64\home\appveyor\nut-win-deps' - Up to date
Build success

Here's the last build which worked, starting out with a cache and dying on timeout while zipping another: https://ci.appveyor.com/project/nut-travis/nut/builds/52500648?full...

This mis-behaves similarly in my private account as well, e.g. at https://ci.appveyor.com/project/jimklimov/nut/builds/52524805 (today) vs. https://ci.appveyor.com/project/jimklimov/nut/builds/52455730?fullL... (2 weeks ago).

1. 1 Posted by jimklimov on 06 Aug, 2025 11:43 PM

   

   Earlier experiments today involved direct pushes to the master branch of upstream or personal repo; for kicks trying a PR build, in case it would behave differently: https://ci.appveyor.com/project/nut-travis/nut/builds/52526491?full...

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 07 Aug, 2025 12:06 AM

   

   There were issues with cache on hosting provider side. They are now must be fixed.
   We are going to re-enable cache tomorrow. Hope that helps. Sorry for the inconvenience.

   • Edit

3. 3 Posted by jimklimov on 07 Aug, 2025 01:28 AM

   

   Ah, great to know as I was banging my head on the wall about whether I corrupted the YAML syntax while reducing its build scope.

   https://status.appveyor.com/ does not mention any reported incidents, and all services claim to be green though...

   • Edit

4. 4 Posted by jimklimov on 07 Aug, 2025 10:16 AM

   

   May I kindly ask to be made aware (here, or via https://status.appveyor.com/) when this caching feature would be re-enabled, so I can avoid trying to re-run those jobs every few hours until their logs do not start with the "Build cache is not configured for the build environment" message. This approach wastes both your resources and mine :)

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 07 Aug, 2025 03:17 PM

   

   Cache has been re-enabled.

   • Edit

6. 6 Posted by jimklimov on 07 Aug, 2025 06:23 PM

   

   Thanks, super - checked that it works again, at least tries to save the caches after a build. Will see if subsequent PR iterations benefit from that :)

   • Edit

7. 7 Posted by jimklimov on 07 Aug, 2025 07:58 PM

   

   They do, issue solved :)

   • Edit