You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we do the known issue validation to see if the provided known issue blob matches the example build provided, we only look at the latest attempt of the build. It would be helpful for devs if this validation looked at older attempts.
It's a common scenario for a dev to rerun a build before knowing whether their issue will repro again, while at the same time filing a known issue for future occurrences.
This might be too expensive to get from Azure DevOps, so let's examine whether it's feasible.
Release Note Category
Feature changes/additions
Bug fixes
Internal Infrastructure Improvements
Release Note Description
Known issue validation now reviews all the failures in a build, including errors of previous attempts
The text was updated successfully, but these errors were encountered:
When we do the known issue validation to see if the provided known issue blob matches the example build provided, we only look at the latest attempt of the build. It would be helpful for devs if this validation looked at older attempts.
It's a common scenario for a dev to rerun a build before knowing whether their issue will repro again, while at the same time filing a known issue for future occurrences.
This might be too expensive to get from Azure DevOps, so let's examine whether it's feasible.
Release Note Category
Release Note Description
Known issue validation now reviews all the failures in a build, including errors of previous attempts
The text was updated successfully, but these errors were encountered: