proj_run_outjob
Execute a named container from an OutJob file to generate fabrication, BOM, or PDF outputs and verify that files were written.
Instructions
Execute a specific output container from an OutJob file.
First use proj_list_outjob_containers to list available
containers, then run the desired one by name. Supports both GeneratedFiles
(Gerber, drill, BOM, etc.) and Publish (PDF) container types.
SUCCESS MEANS A FILE WAS WRITTEN. Running a container proves only
that Altium was asked to. One bound to a managed release, or with
its outputs switched off, runs cleanly and writes nothing, and
this used to report success: true with an output_dir that
had never been created. output_dir is now checked afterwards,
and success is true only when a file under it was written or
changed after the run started.
That check covers output_dir and nothing else. A container
that writes somewhere else reads as success: false, and
reason says what was examined, so a caller who knows where
the output really goes can look there.
Args: container_name: Name of the output container to execute outjob_path: Path to the .OutJob file. If omitted, uses the first OutJob found in the focused project. fresh_window_seconds: files modified up to this many seconds before the run started still count as written, for file systems with coarse timestamps. Default 5s.
Returns:
success, container_name, container_type,
output_dir, output_dir_exists, files_written (a
count), written (up to 50 paths), and reason when
nothing was written.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| outjob_path | No | ||
| container_name | Yes | ||
| fresh_window_seconds | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||