Run Telion Batch in CI
Execute a trusted TLN workflow with bounded runtime, machine-readable progress, transactional output, and stable exit handling.
Use an explicit input, a distinct output path, a bounded timeout, and JSON progress records. The output TLN is committed only after the workflow completes and the staged project passes validation.
Command
telionbatch -ifile model.tln -ofile solved.tln -log solve.log --timeout 900 --json-progress
The packaged executable and source launcher consume the same command specification, so --help, parser defaults, and this reference remain aligned.
Exit handling
| Exit | Meaning | CI action |
|---|---|---|
| 0 | Output committed | Publish the solved TLN and logs |
| 2 | Command or trust rejection | Correct arguments or approve the workflow source |
| 3 | Input or model validation failed | Reject the model artifact |
| 4 | Workflow or solve failed | Inspect stderr, the text log, and any progress records |
| 5 | License rejected execution | Restore an authorized runtime identity |
| 6 | Cancelled or timed out | Preserve logs; retry only after reviewing the limit |
| 7 | Persistence or unexpected failure | Treat the output as uncommitted |
Note. Schedulers should use the process exit status as the primary success signal and retain JSON progress as structured diagnostics. A partial output path is not evidence of a committed solve.
HPC boundary
Allocate threads and accelerators through the scheduler and the saved Telion solver configuration. Batch does not invent an MPI topology or bypass the installed license and trust policies.