(hinoka is more of an owner of BuildInfo than I am)

The problem is the annotations isn't outputting end time:
https://luci-milo.appspot.com/raw/build/logs.chromium.org/chromeos/bb/chromiumos.tryserver/release/18095/+/recipes/annotations
So there's a problem on the recipe/client side too.

nodir@: Since we have a buildbot emulation layer, do you think we can recommend ChromeOS to use the GetBuildbotBuildJSON endpoint instead?
https://luci-milo.appspot.com/rpcexplorer/services/milo.Buildbot/GetBuildbotBuildJSON?request={%20%20%20%20%22master%22:%20%22chromiumos.tryserver%22,%20%20%20%20%22builder%22:%20%22release%22,%20%20%20%20%22buildNum%22:%2018095}

We originally asked ChromeOS to use BuildInfo because we thought that would be the LUCI endpoint going forward, but the design has shifted since then.

But GetBuildbotBuildJSON does not work for swarming builds? We are looking for an API that has through information for both swarming and buildbot builds :-) 

i am not sure how emulation in GetBuildbotBuildJSON will help in this case.

workaround: use buildbucket API (don't you already use it?)
https://apis-explorer.appspot.com/apis-explorer/?base=https://cr-buildbucket.appspot.com/_ah/api#p/buildbucket/v1/buildbucket.get?id=8960871244673031312&_h=1&
has completed_ts

Thanks Nodir, I was using Buildbucket API for more high level summary such as how many slave builds passed for one master build, and Milo.BuildInfo for more details stage and timing. It is indeed a good idea to start using Buildbucket for build overall start/finish time as well.

With that said, the detailed stage information is still important, and please let me know if Milo.BuildInfo is the right way to go down :-) 

Thanks a lot Nodir and Ryan! 

BuildInfo's future is at least very unclear, but we don't have anything better to offer at this point. Ideally we provide a proper API that works for GE and GE does not use BuildInfo (that sometimes works and sometimes does not).

I've created https://docs.google.com/document/d/1ZV3RbxR23R0NkVeKofQumdluPlz0HCBFa6k0a5ok0T4/edit#
to collect GE's API requirements