Successful lint tasks can precede integration tests as a dependency

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: CI
    • 1
    • 1
    • Not Needed
    • None
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Use Case

      As a driver engineer
      I want failing lint to cancel jobs which depend on it
      So that compute cost is not accrued unnecessarily, and failure cause is clear

      User Experience

      • The 'lint' task in evergreen should precede all jobs which inherently rely on it (if lint fails, there's really no reason to run the other jobs)

      Dependencies

      • N/A

      Risks/Unknowns

      • None

      Acceptance Criteria

      Implementation Requirements

      • Failing lint checks should short-circuit the rest of the CI, successful lint checks should continue running the rest of the CI test suite.

      Testing Requirements

      • N/A

      Documentation Requirements

      • N/A

      Follow Up Requirements

      • This practice should have alignment across all repo's we maintain

       

            Assignee:
            Pavel Safronov
            Reporter:
            Johnathan Martell
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: