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.
| Parameter | Description |
|---|---|
|
|
Jenkins server base URL, such as |
| Parameter | Description |
|---|---|
|
|
Environment variable name containing the Jenkins API token.
Example: |
|
|
File path containing the Jenkins API token.
Alternative to |
|
|
Kubernetes or OpenShift namespace where Red Hat Trusted Artifact Signer is deployed.
If provided and |
| Parameter | Description |
|---|---|
|
|
Override Rekor endpoint URL.
Example: |
|
|
Override Fulcio endpoint URL.
Example: |
|
|
Override TUF endpoint URL.
Example: |
|
|
Override Timestamp Authority endpoint URL.
Example: |
|
|
Override OIDC issuer URL.
Example: |
|
|
Override OIDC client ID.
Example: |
| Parameter | Default | Description |
|---|---|---|
|
|
|
Set output mode.
Valid values: |
|
|
|
Set output format.
Valid values: |
|
|
Auto-generated |
File path for |
Example invocations Copy linkLink copied!
- 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