Automate Google Cloud Build
HumDay reads Google Cloud Build’s own published API description and derives 6 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Google Cloud Build is
Creates and manages builds on Google Cloud Platform.
API host: cloudbuild.googleapis.com
What HumDay can do in Google Cloud Build
4 documented operations change something in Google Cloud Build.
- POSTCreates a WorkerPool to run the builds, and returns the new worker pool.
/v1alpha2/{parent}/workerPools - DELETEDeletes a WorkerPool.
/v1alpha2/{name} - PATCHUpdates a WorkerPool.
/v1alpha2/{name} - POSTStarts asynchronous cancellation on a long-running operation.
/v1alpha2/{name}:cancel
What HumDay can read from Google Cloud Build
These are the operations a schedule or a trigger can watch.
- GETReturns details of a WorkerPool.
/v1alpha2/{name} - GETLists WorkerPools by project.
/v1alpha2/{parent}/workerPools
How automating Google Cloud Build works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Cloud Build account.
- Grant access, then go live. You approve the specific Google Cloud Build operations it may use — and only those.
Automate Google Cloud Build with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Cloud Build automation
- Can HumDay connect to Google Cloud Build?
- Yes. HumDay reads Google Cloud Build's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 6 operations are documented.
- Do I need to write code to automate Google Cloud Build?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Cloud Build account.
- What can HumDay do in Google Cloud Build?
- 4 of the 6 documented operations change something in Google Cloud Build, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Cloud Build account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Cloud Build is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Cloud Build at cloudbuild.googleapis.com/$discovery/rest?version=v1alpha2. Descriptions are the provider’s own words, not ours. Last published 2022-12-05.