[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: run.stableId
I think we should allow multiple levels, so either of these is ok – it’s up to the engineering system to decide the appropriate level of bucketing:
I think we should add it, for precisely the reason you cite, bucketing at the stable id level. You might do this in order to organize all tool breaks for both the x86 and amd64 instances of a tool run.
Nightly security tools run for Contoso service
Ping on this. Do we really need the namespacing, given my argument below?
As I understand it, the goal is to bucket together runs of the same type, so that a result management system can:
That doesn’t require namespaced tags. It works whether run.stableId contains "Nightly security tools run/x64 release optimized" or whether it contains "Nightly security tools run x64 release optimized".
The only reason you’d need namespacing is if there’s some other scenario that needs to bucket together every "Nightly security tools run", regardless of the build configuration.