Jenkins scanner parameters

The TAS Integrator Jenkins scanner accepts parameters that control connection settings, endpoint discovery, and output formatting. Understanding these parameters helps you customize scans for different environments and output requirements.

Table 1. Required parameters
Parameter Description

jenkins_url

Jenkins server base URL, such as https://jenkins.example.com.

Table 2. Optional connection parameters
Parameter Description

auth_env

Environment variable name containing the Jenkins API token. Example: JENKINS_API_TOKEN. Generate API tokens in Jenkins at Manage Jenkins Manage Users Configure API Token. If not provided, the scanner attempts unauthenticated access.

auth_file

File path containing the Jenkins API token. Alternative to auth_env for token authentication.

namespace

Kubernetes or OpenShift namespace where Red Hat Trusted Artifact Signer is deployed. If provided and kubectl is available, the scanner automatically discovers endpoint URLs from custom resource status fields.

Table 3. Optional endpoint override parameters
Parameter Description

rekor_url

Override Rekor endpoint URL. Example: https://rekor.tas.example.com. If not provided, the scanner attempts auto-detection from environment variables, Kubernetes custom resources, or RHEL configuration files.

fulcio_url

Override Fulcio endpoint URL. Example: https://fulcio.tas.example.com.

tuf_url

Override TUF endpoint URL. Example: https://tuf.tas.example.com.

tsa_url

Override Timestamp Authority endpoint URL. Example: https://tsa.tas.example.com/api/v1/timestamp. Ensure the URL includes the /api/v1/timestamp path suffix.

oidc_issuer

Override OIDC issuer URL. Example: https://keycloak.example.com/auth/realms/trusted-artifact-signer.

oidc_client_id

Override OIDC client ID. Example: trusted-artifact-signer.

Table 4. Optional output parameters
Parameter Default Description

output

display

Set output mode. Valid values: display (show in conversation), save (write to file), or both (show and save).

format

markdown

Set output format. Valid values: markdown or yaml.

output_path

Auto-generated

File path for save and both output modes. If not provided, the scanner generates a path based on the scan timestamp and CI/CD platform. Example: jenkins-integration-blueprint-20260903-143022.md.

Example invocations

Display blueprint with auto-detected endpoints
/tas-integrator:scan-jenkins

jenkins_url: https://jenkins.example.com
auth_env: JENKINS_API_TOKEN
namespace: trusted-artifact-signer
Save the blueprint to a file with explicit endpoints
/tas-integrator:scan-jenkins --output=save

jenkins_url: https://jenkins.example.com
rekor_url: https://rekor.tas.example.com
fulcio_url: https://fulcio.tas.example.com
tuf_url: https://tuf.tas.example.com
Save the blueprint in YAML format
/tas-integrator:scan-jenkins --output=save --format=yaml

jenkins_url: https://jenkins.example.com
auth_env: JENKINS_API_TOKEN