Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Fix broken links#945

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NimRegev merged 8 commits intomasterfromfix-broken-links
Mar 11, 2024
Merged
Show file tree
Hide file tree
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion_docs/example-catalog/ci-examples/git-checkout.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -107,7 +107,7 @@ max-width="50%"
This is the recommended way of creating re-usable pipelines in Codefresh.

## Cloning a repository with Codefresh Runner
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:

`codefresh.yml`
Expand Down
6 changes: 3 additions & 3 deletions_docs/installation/runner/behind-the-firewall.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -9,7 +9,7 @@ redirect_from:
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.

## Running Codefresh in secure environments
Expand DownExpand Up@@ -126,7 +126,7 @@ steps:
Once you trigger the pipeline, the Codefresh Build Runtimes communicates with your private Git instance and checks out code.

>**NOTE**
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.

Expand All@@ -136,7 +136,7 @@ You can also use a [network proxy]({{site.baseurl}}/docs/pipelines/steps/git-clo
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:

Expand Down
2 changes: 1 addition & 1 deletion_docs/integrations/codefresh-api.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -367,7 +367,7 @@ Encrypted variables cannot be read back by exporting the pipeline.

### Runtime environment

The `runtimeEnvironment` selects the cluster that will execute the pipeline (mostly useful for organizations using the [Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/))
The `runtimeEnvironment` selects the cluster that will execute the pipeline (mostly useful for organizations using the [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/)).

{: .table .table-bordered .table-hover}
| Field name | Parent field | Type | Value |
Expand Down
4 changes: 3 additions & 1 deletion_docs/integrations/kubernetes.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -738,7 +738,9 @@ Codefresh also offers a simple solution for [templating]({{site.baseurl}}/docs/c

## Using a cluster for running CI/CD pipelines

Finally you can also use the [Codefresh Runner]({{site.baseurl}}/installation/docs/runner/install-codefresh-runner/) to run pipelines in your cluster.

Finally you can also use the [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner//) to run pipelines in your cluster.




Expand Down
2 changes: 1 addition & 1 deletion_docs/integrations/secret-storage.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -97,7 +97,7 @@ where:
## Secret store setup for Codefresh Runner installation


For [Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/) installations, you can also store secrets in your own runtime.
For [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) installations, you can also store secrets in your own runtime.

### Set up runtime secret store in Codefresh UI

Expand Down
2 changes: 1 addition & 1 deletion_docs/kb/articles/set-shm-size-for-container.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -12,7 +12,7 @@ support-reviewed: 2023-04-18 LG

## Overview

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).

## Details

Expand Down
2 changes: 1 addition & 1 deletion_docs/pipelines/pipeline-caching.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -200,7 +200,7 @@ This means that unlike other CI solutions where you have to manually describe wh
The main choice that you have is which files to place on the volume. For example, Node.js uses the folder `node_modules` for its dependencies which are placed under the project folder [which is automatically placed under the volume]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/#cloning-the-source-code). So all contents of `node_modules` will be cached by default without any further action on your part.

>**NOTE**
If you are using [Codefresh on-premises]({{site.baseurl}}/docs/installation/codefresh-on-prem/), this kind of caching is not available for the built-in runtime.<br>You need to use the [Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/) with your own runtime to activate volume caching.
If you are using [Codefresh on-premises]({{site.baseurl}}/docs/installation/installation-options/on-premises/), this kind of caching is not available for the built-in runtime.<br>You need to use the [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) with your own runtime to activate volume caching.

The simplest way to see this caching mechanism in action is this pipeline:

Expand Down
2 changes: 1 addition & 1 deletion_docs/pipelines/pipelines.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -403,7 +403,7 @@ max-width="50%"
%}

**Configure runtime environment**<br>
As an account admin, if the account is not configured with a runtime environment, Codefresh displays the steps to [install the Runner]({{site.baseurl}}/docs/installation/codefresh-runner/).
As an account admin, if the account is not configured with a runtime environment, Codefresh displays the steps to [install the Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/).

{% include
image.html
Expand Down
2 changes: 1 addition & 1 deletion_docs/pipelines/steps/approval.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -153,7 +153,7 @@ max-width="90%"
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.

>**NOTE**
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.

## Controlling the rejection behavior

Expand Down
4 changes: 2 additions & 2 deletions_docs/pipelines/steps/git-clone.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -190,7 +190,7 @@ steps:

## Check out code using the Codefresh Runner

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:

`codefresh.yml`
Expand DownExpand Up@@ -452,7 +452,7 @@ steps:

## Using Git behind a proxy

If you use the [Codefresh Runner]({{site.baseurl}}/docs/installation/codefresh-runner/) and need to use a network proxy in your clone step you need to set the [variables]({{site.baseurl}}/docs/pipelines/variables/) `HTTP_PROXY` and/or `HTTPS_PROXY` in the pipeline
If you use the [Codefresh Runner]({{site.baseurl}}/docs/installation/runner/install-codefresh-runner/) and need to use a network proxy in your clone step you need to set the [variables]({{site.baseurl}}/docs/pipelines/variables/) `HTTP_PROXY` and/or `HTTPS_PROXY` in the pipeline
and then activate the property `use_proxy: true` in the clone step. Example:

`codefresh.yml`
Expand Down
2 changes: 1 addition & 1 deletion_docs/quick-start/gitops-quick-start/runtime.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -46,7 +46,7 @@ kubectl annotate --overwrite crds $(kubectl get crd | grep argoproj.io | awk '{p
### Tunnel-based Runtime
Hybrid GitOps Runtimes support tunnel-based, ingress-based, and service-mesh-based access modes.
For the quick start, we'll use the tunnel-based mode which is the default access mode that does not require an ingress controller.
For details on these access modes, review [GitOps Runtime architecture]({{site.baseurl}}/docs/installation/runtime-architecture/#gitops-runtime-architecture).
For details on these access modes, review [GitOps Runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).

### GitHub as Git provider
Hybrid GitOps Runtimes require a Git Runtime token for authentication to the Git installation repository based on your Git provider, and a Git user token to authenticate Git-based actions for the Runtime.
Expand Down
2 changes: 1 addition & 1 deletion_posts/2019-12-31-january-december-classic.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -73,7 +73,7 @@ description: "Changelog for Pipelines 2019 (Classic)"
- 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/)

## April 2019
Expand Down
18 changes: 9 additions & 9 deletions_posts/2020-12-31-january-december-classic.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -7,9 +7,9 @@ description: "Changelog for Pipelines 2020 (Classic)"
## December 2020
- 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)
Expand All@@ -20,14 +20,14 @@ description: "Changelog for Pipelines 2020 (Classic)"
- 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)

## October 2020
- 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/)

## September 2020
Expand All@@ -51,7 +51,7 @@ description: "Changelog for Pipelines 2020 (Classic)"
- Check if a variable exists - [documentation]({{site.baseurl}}/docs/pipelines/conditional-execution-of-steps/#execute-steps-according-to-the-presence-of-a-variable)

## June 2020
- 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)
Expand All@@ -63,7 +63,7 @@ description: "Changelog for Pipelines 2020 (Classic)"
- 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)

## April 2020
Expand DownExpand Up@@ -115,7 +115,7 @@ description: "Changelog for Pipelines 2020 (Classic)"
- 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/)

## January 2020
Expand All@@ -124,4 +124,4 @@ description: "Changelog for Pipelines 2020 (Classic)"
- 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/)
2 changes: 1 addition & 1 deletion_posts/2022-10-15-october-gitops.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -15,7 +15,7 @@ We have changed the routing mechanism for hybrid runtimes. URL requests and webh

The change is effective from runtime version 0.0.543 and higher. If you already have runtimes installed, this change does not require any action from you, both to upgrade to the new runtime version or retain existing runtimes. Older runtimes continue to use the ingress controller for routing purposes.

See the description for Request Routing Service in [Hybrid runtime architecture]({{site.baseurl}}/docs/installation/runtime-architecture/#gitops-runtime-architecture).
See the description for Request Routing Service in [Hybrid runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).

### More Git providers for runtimes

Expand Down
3 changes: 1 addition & 2 deletions_posts/2022-11-15-november-gitops.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -12,8 +12,7 @@ Simplify installation without compromising on security with our tunnel-based ins
Tunnel-based runtimes use tunneling for communication between the customer cluster and the Codefresh platform, with the customer cluster initiating the tunneling request. Simply add the flag `--access-mode` with `tunnel` as the value and you have your tunnel-based runtime without an ingress controller.

See:

* [Tunnel-based runtime architecture]({{site.baseurl}}/docs/installation/runtime-architecture/#gitops-runtime-architecture)
* [Tunnel-based runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/)
* [Runtime flags]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/#runtime-flags)
* [Tunnel-based runtime flags]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/#tunnel-based-runtime-flags)

Expand Down
2 changes: 1 addition & 1 deletion_posts/2023-09-30-sept-release-notes.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -88,7 +88,7 @@ Helm has become the default installation method for the Codefresh Runner. This c

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.



Expand Down
[8]ページ先頭
©2009-2025 Movatter.jp