Skip to content

Run Workflow-to-Python verification only when relevant files change #9523

Description

@kz930

Feature Summary

The Workflow-to-Python verification runs every operator two ways: on the platform and as the exported Python script. Then it compares the two results. It runs inside the workflow-compiling-service leg of platform-integration, so its trigger is too broad in one place and too narrow in another.

It runs on PRs that cannot change either result, for example a PR that only touches file-service or config-service.

It does not run on PRs that can change the platform result. A change to amber's Python runtime under amber/src/main/python is one example, because Python operators run through it during verification.

Proposed Solution or Design

Give verification its own CI stack in precheck. Run it only when a PR touches one of these:

Path Why
common/workflow-operator/** Operator executors and the export code
common/workflow-core/** Tuple, schema and type classes used by both sides
workflow-compiling-service/** The translator and the verification framework
amber/src/main/python/**, amber/src/main/protobuf/** The Python runtime that Python operators run on
amber/*requirements*.txt Library versions used by both sides
build.sbt, project/**, .github/** Build and CI changes

PRs that only touch the frontend, the other services, the amber Scala engine or docs would skip it.

A path list can miss an indirect dependency. As a safety net, the full verification could also run on every push to main.

Affected Area

Deployment / Infrastructure

Activity

  1. added theissue type on Nov 17, 2026
  2. kz930 commented on Nov 17, 2026

    @kz930
    ContributorAuthor

    /unparent-issue #8325

  3. added a commit that references this issue on Nov 18, 2026
    f10ea68
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions