Skip to content

Support running custom targets locally when using Remote Run #5399

@mirinae3145

Description

@mirinae3145

Hi,
I'm adding custom (platform) targets via AddCustomTarget() and encountered inconsistent behavior.

Issue

  • When running pio remote run -t custom_target, they are locally filtered out because they don't belong to predefined categories such as clean or fs family.
  • As a result, custom targets are silently ignored in the local execution (maybe they ran on remote).

Expected

Custom targets are

  1. executed locally, or
  2. on both machines.

Question

  1. Is there a way to mark a custom target as “allowed for local execution”?
  2. Can the filtering logic be bypassed or extended so that custom targets are passed through to local cmd_run?

I think forcing remote option (-r) is not the solution I'm looking for.
Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions