- docs
- Publish and integrate
- Publish and integrate
- Integrations
- Integrate OCX
Integrate OCX
Pick the system you want to connect to OCX, and open the page that shows the shortest working setup.
Run OCX in a pipeline
- Use OCX in GitHub Actions puts a pinned toolchain’s
PATHentries and variables in every step. - Use OCX in GitLab CI does the same for script jobs and step runner jobs.
- Run OCX unattended in a pipeline lists the settings that make a job reproducible and offline-safe.
- Authenticate to GHCR and ECR gives a job credentials for a private registry.
- Publish packages from CI pushes, signs and promotes a package with an SBOM.
Connect other tools
- Use OCX in an editor shares the toolchain with VS Code and any other editor.
- Dev Container Feature installs OCX and restores the project toolchain with one line in
devcontainer.json. - Docker covers the official image and baking a toolchain into your own.
- Use OCX with Bazel lists what
rules_ocxasks of OCX. - Use OCX with Python drives OCX from Python and ships a locked Python application.
- Read OCX output from a script parses JSON, exit codes and the error document.
Work behind a proxy
- Proxy and corporate CA sets the proxy variables and the certificate roots.
Other integrations
Project documentation lives on separate sites: rules_ocx (Bazel), ocx-sdk (Python) CMake and the Dev Container Feature.