Today, CrOS Gerrit already displays the first *release* that contains a particular CL. This feature tracks adding support for also rendering what was the first post-submit *build* that contained the CL. This information is more relevant to sheriffs than a release version number which might be many hours away from completing. To do this, we would give Buildbucket a first-class understanding of the SHA1 (Build.input.gitiles_commit) the master repo commit that was used to build. We also need to index those build in a linear fashion (crbug.com/851585). Then, a new, additional Gerrit plugin would be created to use that metadata to compute the first build (in a particular builder) in which a CL appeared.
The goal is to render where a CL landed, what CL’s were between build A and B, and to display a small summary of that status in Gerrit.
However, CrOS’s source tree is currently based on Repo instead of Git Submodules and so mismatch may occur.

The goal is to render where a CL landed, what CL’s were between build A and B, and to display a small summary of that status in Gerrit.

However, CrOS’s source tree is currently based on Repo instead of Git Submodules and so mismatch may occur.

This is lower priority than other features and some details remain to be worked out. Likely we won't look at this until late Q1.
 

Today, CrOS Gerrit already displays the first *release* that contains a particular CL. This feature tracks adding support for also rendering what was the first post-submit *build* that contained the CL. This information is more relevant to sheriffs than a release version number which might be many hours away from completing. To do this, we would give Buildbucket a first-class understanding of the SHA1 (Build.input.gitiles_commit) the master repo commit that was used to build. We also need to index those build in a linear fashion (crbug.com/851585). Then, a new, additional Gerrit plugin would be created to use that metadata to compute the first build (in a particular builder) in which a CL appeared.

The goal is to render where a CL landed, what CL’s were between build A and B, and to display a small summary of that status in Gerrit.

However, CrOS’s source tree is currently based on Repo instead of Git Submodules and so mismatch may occur.

This is lower priority than other features and some details remain to be worked out. Likely we won't look at this until late Q1.