Currently CircleCI monorepo uses path-filtering to generate a set of parameters, which can be used by the 2.1 configuration to enable or disable entire workflows, but not select jobs (which lack a when clause). Unfortunately this prevents any ability to execute E2E testing (or any ensuing workflow) , since we do not provide for any means to chain workflows.

As it stands, CircleCI does not provide the ability to execute E2E testing (or any ensuing workflow) based on the outcome of a monorepo build where multiple workflows have been triggered. This denies customers the ability to execute e2e tests or conclusion workflows like deployments once individual components have completed their build & test activities.

To be successful we would like to see the when clause added to jobs within a workflow (this allowing monorepo to be concurrent streamds in single workflow with fan-in jopb at end) or the ability for workflow to define a require condition like jobs do so we may chain multiple workflows