Automate Google Remote Build Execution
HumDay reads Google Remote Build Execution’s own published API description and derives 8 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 Remote Build Execution is
Supplies a Remote Execution API service for tools such as bazel.
API host: admin-remotebuildexecution.googleapis.com
What HumDay can do in Google Remote Build Execution
5 documented operations change something in Google Remote Build Execution.
- POSTSends a test notification to the specified instance.
/v1alpha/{name}:testNotify - POSTCreates a new instance in the specified region.
/v1alpha/{parent}/instances - POSTCreates a new worker pool with a specified size and configuration.
/v1alpha/{parent}/workerpools - DELETEDeletes the specified worker pool.
/v1alpha/{name} - PATCHUpdates an existing worker pool with a specified size and/or configuration.
/v1alpha/{name}
What HumDay can read from Google Remote Build Execution
These are the operations a schedule or a trigger can watch.
- GETGets the latest state of a long-running operation.
/v1alpha/{name} - GETLists instances in a project.
/v1alpha/{parent}/instances - GETLists worker pools in an instance.
/v1alpha/{parent}/workerpools
How automating Google Remote Build Execution 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 Remote Build Execution account.
- Grant access, then go live. You approve the specific Google Remote Build Execution operations it may use — and only those.
Automate Google Remote Build Execution 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 Remote Build Execution automation
- Can HumDay connect to Google Remote Build Execution?
- Yes. HumDay reads Google Remote Build Execution's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 8 operations are documented.
- Do I need to write code to automate Google Remote Build Execution?
- 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 Remote Build Execution account.
- What can HumDay do in Google Remote Build Execution?
- 5 of the 8 documented operations change something in Google Remote Build Execution, and 3 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Remote Build Execution 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 Remote Build Execution is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Remote Build Execution at admin-remotebuildexecution.googleapis.com/$discovery/rest?version=v1alpha. Descriptions are the provider’s own words, not ours. Last published 2023-03-23.