firebase-tools: Firebase deploy stuck at "cleaning up build files..."
[REQUIRED] Environment info
firebase-tools: 9.16.0
**Platform:**macOS
[REQUIRED] Test case
Deploy functions using firebase deploy --only functions
[REQUIRED] Steps to reproduce
Deploy functions using firebase deploy --only functions
[REQUIRED] Expected behavior
The deploy should complete after the logs functions: cleaning up build files...
[REQUIRED] Actual behavior
The logs are stuck at functions: cleaning up build files...
and requires a Ctrl+C
to regain terminal.
The above behaviour does not occur everytime. Is it important for it to finish, or can I ignore the fact that it gets stuck and continue without having to try and re-deploy?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 21 (8 by maintainers)
firebase logout and then login fixed it for me.
Goodness. This issue sat in my inbox for an inexcusable amount of time. Sorry; I don’t get to code much these days and didn’t check GitHub for a few weeks. The code to deploy your functions has been completely rewritten between those two versions. Some changes intended to improve reliability and some also intended to help performance.
Can you file a support ticket at https://firebase.google.com/support to make sure you get the attention you deserve? A firebase-debug.log would let us see pretty quickly where the failures are and help us fix whatever regression is hitting you.
It shouldn’t be getting stuck, though it’s not fatal if you ctrl + c to kill that part of the process; it happens after your functions are already done deploying. Out of curiosity, let’s try absolutely cleaning your artifacts and seeing if you continue to get stuck afterwards. Try running the following commands:
This process will check your per-metro Google Container Repository buckets for the
gcf
folder and recursively delete its contents. If you’ve been putting your own images in that directory they will be deleted by this command as well. Can you run this command to completion and then write back in a week or so whether you continue to see deploys get stuck?