I believe that the TaskCluster-y way of solving this problem is to use the index. We want a hash that captures the state of GV, just like we have hashes that capture the state of toolchains. There's lots of support for this but toolchains might be the only place that really _use_ that support. That is, you want things that will produce the same GV to re-use an existing one, and -- I claim -- it's worth the engineering effort to try to solve that problem.
Bug 1882160 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I believe that the TaskCluster-y way of solving this problem is to use the TaskCluster index. We want a hash that captures the state of GV, just like we have hashes that capture the state of toolchains. The index then lets us find tasks that produced the expected index. There's lots of support for this but toolchains might be the only place that really _exercise_ that support. That is, you want things that will produce the same GV to re-use an existing one, and -- I claim -- it's worth the engineering effort to try to solve that problem.