Skip to content

Decide if .ci.yaml parser should infer "required" runIf deps #160874

@matanlurey

Description

@matanlurey

This is a TODO to discuss with @jtmcdole and @christopherfujino after the holidays as a part of flutter/cocoon#4137.

As of flutter/cocoon#4137, if runIf is used, both:

  • DEPS
  • .ci.yaml (or engine/src/flutter/.ci.yaml)

... are required entries. @yjbanov asked in flutter/cocoon#4137 if it would be possible to have the .ci.yaml parser auto-infer these entries, instead of requiring them explicitly for each task. I can see PROs and CONs to both approaches, so we should discuss this informally before making a decision.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: proposalA detailed proposal for a change to Flutterc: tech-debtTechnical debt, code quality, testing, etc.team-infraOwned by Infrastructure teamtriaged-infraTriaged by Infrastructure team

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions