(In reply to Mike Hommey [:glandium] from comment #5) > Although... I guess we could swipe that in the build_metrics framework.... It all depends what registering the vcs framework on perfherder does to the data that has been there all along? Would all that data be visible, or would only new data be available? Only new `vcs` data will be available. Old one has been skipped on PERHERDER_DATA parse time.
Bug 1572356 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Mike Hommey [:glandium] from comment #5) > Although... I guess we could swipe that in the build_metrics framework.... It all depends what registering the vcs framework on perfherder does to the data that has been there all along? Would all that data be visible, or would only new data be available? Only new `vcs` data will be available. Old one has been skipped on PERHERDER_DATA parse time. It will create a new dropdown item in Perfherder, similar to `build_metrics`, `talos`, `awsy`, `raptor`. So, if `vcs` could me mixed into `build_metrics`, I suggest go with 1st option.
(In reply to Mike Hommey [:glandium] from comment #5) > Although... I guess we could swipe that in the build_metrics framework.... It all depends what registering the vcs framework on perfherder does to the data that has been there all along? Would all that data be visible, or would only new data be available? Only new `vcs` data will be available. Old one has been skipped on PERHERDER_DATA parse time. It will create a new dropdown item in Perfherder, similar to `build_metrics`, `talos`, `awsy`, `raptor`... So, if `vcs` could me mixed into `build_metrics`, I suggest go with 1st option.