This is the recommended way of creating re-usable pipelines in Codefresh.

If you have the[Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/) installed, you need to use

If you have the[Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) installed, you need to use

the fully qualified path of the Git repository:

toc:true

As described in[Codefresh Runner]({{site.baseurl}}/docs/installation/runner/), the Hybrid Runner is required to run Codefresh pipelines.

As described in[Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner), the Hybrid Runner is required to run Codefresh pipelines.

This articles focuses on how the Runner works within infrastructure behind firewalls.

Once you trigger the pipeline, the Codefresh Build Runtimes communicates with your private Git instance and checks out code.

Currently there is a limitation on the location of the`codefresh.yml` file. Only the[inline mode]({{site.baseurl}}/docs/pipelines/pipelines/#writing-codefresh-yml-in-the-gui) is supported by default. You will need to install the[App-Proxy]({{site.baseurl}}/docs/installation/codefresh-runner/#app-proxy-installation) to be able to use the YAML from Repository.

Currently there is a limitation on the location of the`codefresh.yml` file. Only the[inline mode]({{site.baseurl}}/docs/pipelines/pipelines/#writing-codefresh-yml-in-the-gui) is supported by default. You will need to install the[App-Proxy]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/#app-proxy-installation) to be able to use the YAML from Repository.

You can also use a[network proxy]({{site.baseurl}}/docs/pipelines/steps/git-clone/#using-git-behind-a-proxy) for the Git clone step.

In the previous section we have seen how a pipeline can check out code from an internal Git repository. We also need to set up a trigger,

so that every time a commit or any other supported event occurs, the Codefresh pipeline is triggered automatically.

If you have installed the[optional app-proxy]({{site.baseurl}}/docs/installation/codefresh-runner/#optional-installation-of-the-app-proxy), adding a trigger can be done exactly like the SAAS version of Codefresh, using only the Codefresh UI.

If you have installed the optional app-proxy, adding a trigger can be done exactly like the SAAS version of Codefresh, using only the Codefresh UI.

If you haven't installed the app-proxy, then adding a Git trigger is a two-step process:

A user wants to have better performance for their containers/builds in their private Kubernetes clusters using the[Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/)(Hybrid).

A user wants to have better performance for their containers/builds in their private Kubernetes clusters using the[Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/)(Hybrid).

If you do decide to keep the volume after an approval, and you are using the SaaS version of Codefresh, the pipeline will still count as "running" against your pricing plan. If you don't keep the volume, the pipeline is stopped/paused while it is waiting for approval and doesn't count against your pricing plan. We advise you to keep the volume only for pipelines that really need this capability.

If you use the[Codefresh Runner]({{site.baseurl}}/docs/installation/behind-the-firewall/) and your[Runner]({{site.baseurl}}/docs/installation/codefresh-runner/) is set up with local volumes, then the volume will only be present if the dind pod is scheduled in the same node once the pipeline resumes. Otherwise the volume will not be reused.

If you use the[Codefresh Runner]({{site.baseurl}}/docs/installation/behind-the-firewall/) and your[Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) is set up with local volumes, then the volume will only be present if the dind pod is scheduled in the same node once the pipeline resumes. Otherwise the volume will not be reused.

If you are using the[Codefresh runner]({{site.baseurl}}/docs/installation/codefresh-runner/), you need to use

If you are using the[Codefresh runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/), you need to use

the fully qualified path of the Git repository:

and then activate the property `use_proxy:true` in the clone step. Example:

- Custom annotations on projects, pipelines, builds -[documentation]({{site.baseurl}}/docs/pipelines/annotations/)

- Deployments with Pulumi -[documentation]({{site.baseurl}}/docs/example-catalog/cd-examples/pulumi/)

- Deployments with Terraform -[documentation]({{site.baseurl}}/docs/example-catalog/cd-examples/terraform/)

- Codefresh Runner installation -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/)

- Codefresh Runner installation -[documentation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/)

- Multiple Dockerhub integrations -[documentation]({{site.baseurl}}/docs/integrations/docker-registries/)

- Get Code Coverage Reports with Coveralls -[documentation]({{site.baseurl}}/docs/example-catalog/ci-examples/coveralls-testing/)

- Codefresh will now use the default branch (e.g.`main`) instead of assuming`master`. This applies to GitHub, GitLab, and Bitbucket -[documentation]({{site.baseurl}}/docs/pipelines/steps/git-clone/)

- App-Proxy now supports GitLab -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#app-proxy-installation)

- App-Proxy now supports GitLab -[documentation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/#app-proxy-installation)

- Helm promotion pipelines can be overridden in the GUI -[documentation]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion/#creating-a-custom-helm-board)

- Internal Registry mirror for the Codefresh runner -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#configure-internal-registry-mirror)

- Internal Registry mirror for the Codefresh runner -[documentation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/#configure-internal-registry-mirror)

- Production and staging deployments guide -[documentation]({{site.baseurl}}/docs/ci-cd-guides/environment-deployments/)

- Escaping YAML in pipelines -[documentation]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/#escaping-strings)

- GitOps dashboard now shows affected services for each release -[documentation]({{site.baseurl}}/docs/ci-cd-guides/gitops-deployments/#working-with-the-gitops-dashboard)

- Getting Code Coverage Reports with Codecov -[documentation]({{site.baseurl}}/docs/example-catalog/ci-examples/codecov-testing/)

- Integrating SonarQube Analysis into your Pipelines -[documentation]({{site.baseurl}}/docs/testing/sonarqube-integration/)

- GitOps deployments -[documentation]({{site.baseurl}}/docs/ci-cd-guides/gitops-deployments/)

- Global volume mounts in the Codefresh runner -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#custom-volume-mounts)

- Global environment variables in the Codefresh runner -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#custom-global-environment-variables)

- Global volume mounts in the Codefresh runner -[documentation](https://artifacthub.io/packages/helm/codefresh-runner/cf-runtime#custom-volume-mounts)

- Global environment variables in the Codefresh runner -[documentation](https://artifacthub.io/packages/helm/codefresh-runner/cf-runtime#custom-global-environment-variables)

- Using Google for SSO -[documentation]({{site.baseurl}}/docs/administration/single-sign-on/sso-google/)

- Setting-up Helm Triggers in your Codefresh pipeline with the Codefresh UI -[documentation]({{site.baseurl}}/docs/pipelines/triggers/helm-triggers/)

- Using the GitHub Container registry as Docker registry -[documentation]({{site.baseurl}}/docs/integrations/docker-registries/github-container-registry/)

- Simplified Git operations with the App Proxy for the Codefresh runner -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#app-proxy-installation)

- Simplified Git operations with the App Proxy for the Codefresh runner -[documentation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/#app-proxy-installation)

- Upgrade Codefresh on-prem -[documentation]({{site.baseurl}}/docs/installation/codefresh-on-prem-upgrade/)

- Check if a variable exists -[documentation]({{site.baseurl}}/docs/pipelines/conditional-execution-of-steps/#execute-steps-according-to-the-presence-of-a-variable)

- New Codefresh Runner installation -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/)

- New Codefresh Runner installation -[documentation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/)

- Using multiple Registry integrations with the same domain -[documentation]({{site.baseurl}}/docs/ci-cd-guides/working-with-docker-registries/#working-with-multiple-registries-with-the-same-domain)

- Multiple Dockerhub integrations -[documentation]({{site.baseurl}}/docs/integrations/docker-registries/other-registries/)

- Global Docker registry prefix/repository -[documentation]({{site.baseurl}}/docs/integrations/docker-registries/#using-an-optional-repository-prefix)

- Masking encrypted variables in logs -[documentation]({{site.baseurl}}/docs/pipelines/variables/#masking-variables-in-logs)

- Restrict Codefresh to specific namespace -[documentation]({{site.baseurl}}/docs/integrations/kubernetes/#restrict-codefresh-access-to-a-specific-namespace)

- Deploy with Kustomize -[documentation]({{site.baseurl}}/docs/example-catalog/cd-examples/deploy-with-kustomize/)

- Installing the Codefresh Runner on a multi AZ GKE cluster -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/)

- Installing the Codefresh Runner on a multi AZ GKE cluster -[documentation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/)

- Masking encrypted variables in logs -[documentation]({{site.baseurl}}/docs/pipelines/variables/#masking-variables-in-logs)

- New UX flow for the signup process

- Updated OneLogin SSO support -[documentation]({{site.baseurl}}/docs/administration/single-sign-on/saml/saml-onelogin/)

- Published Codefresh Platform IPs -[documentation]({{site.baseurl}}/docs/integrations/kubernetes/#prerequisites)

- Installing the Codefresh Runner in AWS -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/#installing-on-aws)

- Installing the Codefresh Runner in AWS -[documentation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/#installing-on-aws)

- Amazon ECS/Fargate deployment example -[documentation]({{site.baseurl}}/docs/integrations/amazon-web-services/)

- Promoting Docker images -[documentation]({{site.baseurl}}/docs/ci-cd-guides/working-with-docker-registries/#promoting-docker-images)

- Using Dockerhub personal access tokens -[documentation]({{site.baseurl}}/docs/integrations/docker-registries/docker-hub/)

- Updated Azure SSO instructions -[documentation]({{site.baseurl}}/docs/administration/single-sign-on/oidc/oidc-azure/)

- Codefresh Runner requirements -[documentation]({{site.baseurl}}/docs/installation/codefresh-runner/)

- Codefresh Runner requirements -[documentation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/)

The new Helm installation for the Runner is described in[Chart Configuration](https://artifacthub.io/packages/helm/codefresh-runner/cf-runtime#chart-configuration){:target="\_blank"} on ArtifactHub.

Refer also to[Codefresh Runner installation]({{site.baseurl}}/docs/installation/codefresh-runner/) in the documentation.

Refer also to[Codefresh Runner installation]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) in the documentation.