15👍
You must enable billing first, then you can enable the Cloud Build service for your project.
6👍
We ran in to an issue where an incomplete deploy (that hung and had to be aborted) had errors setting some internal service account permissions and kept getting the “Cloud Build has not been used in project before or it is disabled” error despite the Cloud Build API being enabled and a billing account set up.
We solved the issue by disabling the Cloud Build API, waiting a couple hours (to ensure the service accounts were deleted), and then re-enabling.
- Django – Import views from separate apps
- Django database delete specific number of entries
- Django on Google App Engine
- Sometimes request.session.session_key is None
5👍
You go that link then click “Enable” button. A popup showed, then click to Set account. (see the picture)
5👍
I solved this problem using the following commands at the root directory of my project:
gcloud init
gcloud components update
After I updated the project settings with my GCP account the problem was solved.
2👍
Had this issue before.
It can simply be a billing issue.
Solution:
- Disable the Cloud Build API
- Attempting to re-enable will possibly result in a billing issue that needs resolving.
TLDR; Turn off and on again.
- Creation of dynamic model fields in django
- How to concatenate two model fields in a Django QuerySet?