Hello,
We are experimenting with implementing Horde Build Health Issues and have encountered a behavior we’d like clarification on.
When using incremental compilation, we have noticed that if a file produces a compiler warning, a build health issue is correctly created. However, on the next changelist, the issue may be automatically closed because the warning disappears since the same file was not recompiled in that build. This can lead to the same warning repeatedly opening and closing across builds, potentially generating repeated notifications for users.
What is the expected or recommended approach when using Horde Build Health Issues with incremental builds? How is Epic addressing this scenario?
One possible solution would be to force full rebuilds, but that has obvious drawbacks in terms of build times. Is there a preferred or supported method to ensure warnings are persistent, for example by forcing recompilation of files that previously emitted warnings until they are fixed?
Thank you,