Improve buildbucket API documentation |
||
Issue descriptionhttps://chromium.googlesource.com/infra/infra/+/master/appengine/cr-buildbucket/doc/index.md does not mention retry command, its client_operation_id and pubsub_callback fields, does not describe format for the lease_expiration_ts etc. Looks like it needs to be updated. It should probably also mention V2 and link its documentation.
,
Nov 30
Found more details in the design doc: https://docs.google.com/document/d/10BH6oSq_UEtdSdhrguEuV4hx-JxY7jzFcgs1OCHcniQ/edit#heading=h.lio3dwa86eek, but this still does not describe how timestamp is to be specified and does not mention pubsub_callback.
,
Nov 30
Lease expiration ts is used only if you schedule a build and lease it at the same time. “Here is work, but I’ll do it myself”. I doubt you need that. Good point about absence or callback in retry. This isn’t implemented. Going forward I’ll implement build scheduling in v2 and document it in go/buildbucket-rpc |
||
►
Sign in to add a comment |
||
Comment 1 by serg...@chromium.org
, Nov 30