-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
Future Sustainability
-
False
-
-
False
-
3
-
None
-
None
-
CORENET Sprint 274, CORENET Sprint 275, CORENET Sprint 276, CORENET Sprint 277, CORENET Sprint 278, CORENET Sprint 279
the linter job for openshift CI doesn't actually run the lint job and probably hasn't for a long time.
it's simply failing at the check for container runtime. In the past it would print a nice debug message and exit 0. Recent changes in upstream now have it with exit 1 and that has started to fail the lint job which blocks PRs.
the team wants to actually have the lint job running and testing. this story tracks the work for that.
- links to
(13 links to)