Closed Sjors-Boom closed 6 years ago
Hi @Sjors-Boom,
thanks for bringing this up and even working on a fix! I've accepted your pull request and I'll make sure it goes live ASAP.
Thanks for helping us out!
Wouter
Dear all,
Thank you very much for the work and support.
We are facing the same issue. For what I see, this should be fixed! Could you please lend us a hand with this problem? What is the current status of this issue?
Thank you a lot!
This fix has not yet been released, has it? Any plans to do this soon?
Build definitions with similar names are included in results.
Steps to reproduce
Create builds with similar names:
Foo.Bar
andFoo.Bar.Gated
Configure Build Health Overview only for build
Foo.Bar.Gated
Run both builds
Result
The overview shows results from both build definitions.
Investigation This line is the culprit:
definitions = definitions.filter(def => customSettings.selectedDefinitions.indexOf(def.name) != -1);
Foo.Bar
is present within stringFoo.Bar.Build
Thus not filtered from the original set of build definitionsproposed solutions
customSettings.selectedDefinitions
and check for full matchcustomSettings.selectedDefinitions
(note: when a build is regenerated and gets a new id it won't be in the results)