Open
Description
Background
Release shepherd edges over the 50% threshold today. To bring it back in line we desperately need an easy was to track, associate, and forward failures from team city.
What kind of contribution is this issue about?
Team city test failures
Details
Automation design could look some like.
- Automatic tagging of tests on team city with an (investigating) label if there is an associated Issue.
- Removing investigating label if the Issue closes.
- Easy UI for creating an issue if not exist (optional)
Thus, an issue existing would be readily apparent and there would be instant forward looking visibility for future BoD as to the state of failure investigation (or lack there or).