tbusot
commented
1 week ago For those stuck with this for, you can deploy in 2 steps reliably when you do a manual deploy, rather than running the job over and over, hoping it succeeds eventually:
First, do a firebase deploy --only functions
If it fails (and it probably will) it's going to fail on some, succeed on hopefully most. At the end of the run, it's going to produce a list of functions that failed to deploy like this:
- Error Failed to update function bioCreated in region us-central1
- Error Failed to update function messageCreated in region us-central1
- Error Failed to update function groupInvitationUpdated in region us-central1Extract that list of functions into a list and re-run deploy like this:
firebase deploy --only "functions:bioCreated, functions:messageCreated, functions:groupInvitationUpdated" and it should succeed.
blidd-google
SherpaMiguel
megastep
mkdior
wesleygonalv
matt-oakes
charlesfries
andrewkrippner
chriswaterbury
toddmotto
[REQUIRED] Environment info
firebase-tools: 13.8.0 or 13.10.2
Platform: ubuntu-latest, via GitHubAction
[REQUIRED] Test case
run
firebase deploy --force --only functions,firestorewith a codebase containing 55 2nd Cloud Functions. In my case it is ran via action w9jds/firebase-action@v13.10.2 (or w9jds/firebase-action@v13.8.0)[REQUIRED] Steps to reproduce
Same as test case
[REQUIRED] Expected behavior
I would expect this deployment to go through since it is below the deployment quota of 80 functions per minute.
[REQUIRED] Actual behavior
Some of the functions fail to deploy with build with the following error:
Build failed with status:
EXPIRED and message: An unexpected error occurred. Refer to build logs: [redacted]. For more details see the logs at [redacted].The build logs are empty and don't contain any useful information other than the build expiring.I can see in Cloud Build console that some of the builds failed:
This happens for about 15 of the 55 functions. Here is a truncated output of the full deploy:
It's actually reopening for #5967 ...