px workspace is just files, a git repo can be the source of truth for your
Prometheux ontologies — validated on every pull request and applied on every merge. px
runs headless in CI: authenticate with environment variables, no interactive login.
Authenticate in CI
Skippx login and set two environment variables (they override any stored config):
${ENV_VAR} must also be present in the environment at apply time.
Validate on pull requests
validate is fully offline — no token, no platform — so it’s a fast, cheap PR gate:
--strict turns warnings into failures so a PR can’t merge with, for example, a
concept-less ontology.
Test logic on pull requests
px test runs Vadalog programs on the
engine and checks the rows they produce, so a PR that changes a rule’s results fails before
it merges. Keep the programs, their *.test.yaml cases and the expected CSVs in the repo,
and publish the JUnit report so the CI system shows each case:
Unlike
validate, px test needs the platform and a running compute machine. Either keep
a machine running for CI, or start one in the job with px compute start and stop it in a
final step that runs if: always(). A machine takes a short while to accept work after it
starts.--replicas 2 (or --replicas auto) to the px test step: it
starts engine workers
beside the machine for the length of the run and removes them at the end, even when the
job is cancelled. Give the step a few extra minutes the first time, while the workers
start. Each worker is billed at the machine’s hourly rate while it runs.
Apply on merge to main
Run
px plan before px apply in the job so the diff (including the downstream re-run
cascade) is captured in the build log for review/audit.Sync the context layer
Apply the context layer the same way. Commit.px/context-state.json so the sync stays idempotent across runs:
Exit codes for gating
CI can gate on exit codes directly (see the command reference):px validate→0PASS, non-zero FAIL.px test→0every check passed,1a check failed,2the tests could not start.px apply→0on success; non-zero if any concept was skipped (with a summary) or on a hard error — so a partial apply fails the job.px plan,px status→0.
Idempotency & state to commit
- Project id in
ontologies/<slug>/prometheux.yaml— commit it so re-apply targets the same ontology (never creates a duplicate). If it’s lost,applyreconciles by ontology name. - Context state
.px/context-state.json— commit it socontext applyupdates rather than re-creates notes.
Corporate runners
px honours HTTPS_PROXY, NO_PROXY, PIP_INDEX_URL, and
REQUESTS_CA_BUNDLE / SSL_CERT_FILE, so it works on locked-down self-hosted runners
behind a proxy with a corporate CA. Install the signed wheel from your internal mirror
instead of the public one-liner. See Installation → Corporate install.
