Jenkins
OX Security integrates with Jenkins to scan Docker-based builds for security issues.
To scan pull requests before they are merged, you must configure Jenkins to provide source and target branch information in the pipeline.
Prerequisites
Docker support: Jenkins must be able to run Docker containers.
Git information: Jenkins must use the Git plugin or be manually configured to provide commit and branch details.
Required environment variables
OX_API_KEY
OX_HOST_URL
The OX platform URL (only if using an on-premise installation).
GIT_URL
The repository URL. Provided by the Git plugin or entered manually.
GIT_COMMIT
The commit SHA. Provided by the Git plugin or replaced with OX_COMMIT_SHA.
GIT_BRANCH
The branch name. Provided by the Git plugin or replaced with OX_SOURCE_BRANCH.
Optional environment variables
OX_TARGET_BRANCH
The target branch name. Recommended when running scans before merging pull requests.
OX_OVERRIDE_BLOCKING
Set to true to override stage failure caused by blocking issues.
OX_TIMEOUT
Maximum duration of the scan, in minutes.
OX_FAIL_ON_TIMEOUT
Set to true to fail the stage if a scan times out.
OX_FAIL_ON_ERROR
Set to true to fail the stage if a system or network error occurs.
Advanced environment variables
OX_DISABLE_SSL_VALIDATION
Set to true to disable SSL certificate validation for self-signed certificates in on-premise environments.
CF_ACCESS_CLIENT_ID
Sent as the CF-Access-Client-Id request header on requests to the OX API. Set this only when your OX deployment sits behind an access proxy that requires service-token headers, such as Cloudflare Access.
CF_ACCESS_CLIENT_SECRET
Sent as the CF-Access-Client-Secret request header on requests to the OX API. Use together with CF_ACCESS_CLIENT_ID.
Integration example (Jenkinsfile)
Last updated