IntelliJ Run/Debug Configuration Portability Between Developer Workstations and CI Agents

Goal: ensure that a Run/Debug configuration that launches successfully on a developer’s workstation also executes without modification on a headless CI or production build agent.

The configuration stores absolute file‑system paths, local environment‑variable values and the IDE‑resolved Project SDK in .idea/workspace.xml or per‑run XML files. When these settings are not portable, the CI agent encounters missing directories, undefined variables or a JDK version mismatch, causing silent failures or class‑version errors.

Which subset of run‑configuration settings should be committed to version control to guarantee reproducibility? How can teams enforce that CI agents use the same JDK and working‑directory semantics as the developer IDE without duplicating configuration?