[Jenkins]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/jenkins/)

For the complete list of arguments you can use, see[CIintegration for GitOpsargument reference](#ci-integration-argument-reference) in this article.

For the complete list of arguments you can use, see[CIintegrationsargument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/ci-argument-reference/).

{:start="4"}

1. To generate a YAML snippet with the arguments, on the top-right, click**Generate Manifest**.

|`CF_JIRA_SERVER_PAT`| The Personal Access Token (PAT) from your Git provider used for authentication to the Jira server, as an alternative to API token-based authentication. <br>When using PAT, configure`CF_JIRA_HOST_URL` instead of`CF_ISSUE_TRACKING_INTEGRATION`.| Optional|

|`CF_JIRA_PROJECT_PREFIX`|Relevant only when you need a Jira integration with either API or PAT authentication.<br> One or more project prefixes in Jira to identify the Jira ticket number to use.<br>**NOTE**: Multiple project prefixes require runtime version 0.1.30 or higher. <br>To specify more than one prefix, use a comma-separated list or a regex. {::nomarkdown}<ul><li>Comma-separated list: <codeclass="highlighter-rouge">DEV,PROD,SAAS</code></li><li>Regex: Regex must start with a front slash <codeclass="highlighter-rouge">/</code> and end with <codeclass="highlighter-rouge">/g</code>. <br>Example: <codeclass="highlighter-rouge">/[A-Z]{2,}-\d+/g</code>.</li></ul>{:/}| Required|

|`CF_JIRA_MESSAGE`| Relevant only when you need a Jira integration with either API or PAT authentication.<br> The Jira issue IDs matching the string to associate with the image.| Required|

|`CF_JIRA_FAIL_ON_NOT_FOUND`| Relevant only when you need a Jira integration with either API or PAT authentication.<br> The report image action when the`CF_JIRA_MESSAGE` is not found. When set to`true`, the report image action is failed.| Required|

|`CF_JIRA_FAIL_ON_NOT_FOUND`| Relevant only when you need a Jira integration with either API or PAT authentication.<br> The report image action when the`CF_JIRA_MESSAGE` is not found. When set to`true`, the report image action is failed.| Required|

[Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)

[Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/)

[Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)

Except for Git branch and Git repo which are required, you can omit other Git provider arguments. Codefresh retrieves the required values from the runtime context selected for the integration.

{{site.data.callout.end}}

For the complete argument reference, see[CI integration for GitOps argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/#ci-integration-argument-reference).

For the complete argument reference, see[CI integration for GitOps argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/ci-argument-reference/).

{: .table .table-bordered .table-hover}

To enrich images with relevant information from Gerrit, incorporate Codefresh's image reporting step into your pipelines/workflows, providing relevant Gerrit arguments.

Look for`CF_GERRIT_` in[CI integration argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/#ci-integration-argument-reference).

Look for`CF_GERRIT_` in[CI integration argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/ci-argument-reference/).

[Shared Configuration Repo]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)

{: .table .table-bordered .table-hover}

| Item| Description|

| ----------| --------|

|`CF_HOST`| Deprecated from v 0.0.460 and higher in CI integrations. Recommend using`CF_RUNTIME_NAME` instead. See[CI integrations argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/#ci-integration-argument-reference).|

|`CF_HOST`| Deprecated from v 0.0.460 and higher in CI integrations. Recommend using`CF_RUNTIME_NAME` instead. See[CI integrations argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/ci-argument-reference/).|

|`GHCR_GITHUB_TOKEN_AUTHENTICATION`| New value for`CF_CONTAINER_REGISTRY_INTEGRATION` argument. Can be selected for GitHub Container (GHCR) registries even when you don’t have a GHCR integration in Codefresh. See[GitHub Action-Codefresh integration settings]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/github-actions/#github-action-gitops-integration-settings).|