blender-pipeline-automation

1# Pipeline Automation
2 
3The execution model is in `blender-core` (`run_in_blender.py` finds Blender and prints only the JSON results).
4 
5## Batch one-liners
6```
7blender -b -P scripts/batch_process.py -- --in "assets/**/*.fbx" --op convert --to glb --out export/
8blender -b -P scripts/batch_process.py -- --in library/ --op report                      # inventory JSON lines
9blender -b -P scripts/batch_process.py -- --in "src/*.blend" --op script \
10    --script ../blender-asset-qa/scripts/qa_check.py --kwargs '{"profile":"game"}'       # QA a whole library
11blender -b -P scripts/batch_process.py -- --in src/ --op script --script ../blender-game-optimization/scripts/make_lods.py \
12    --kwargs '{"rename":true}' --save-to processed/                                      # LODs for every file
13```
14Each file is streamed as one JSON line with `ok`, timing and results. Failures don't stop the batch, and the summary lists them. **Parallel**: start N processes with `--shard 0/N` … `--shard N-1/N` (Blender uses one core for Python, so processes scale with CPU/GPU count).
15 
16## Headless CLI essentials
17| Flag | Meaning |
18|---|---|
19| `-b` | background, no UI. Put it **first** |
20| `file.blend` | open before running scripts. Order matters: args run left to right |
21| `-P script.py` / `--python-expr "..."` | run Python |
22| `--python-exit-code 1` | non-zero exit if the script raises (CI) |
23| `--factory-startup` | ignore user prefs/add-ons (reproducible). Bundled add-ons still load |
24…