You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/troubleshooting/common-issues/could-not-tag-image.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ toc: true
18
18
19
19
##Possible cause
20
20
21
-
This issue occurs because of a race condition when multiple builds try to push the same image at the same time[to a Docker registry]({{site.baseurl}}/docs/docker-registries/push-image-to-a-docker-registry/).
21
+
This issue occurs because of a race condition when multiple builds try to push the same image at the same time[to a Docker registry]({{site.baseurl}}/docs/example-catalog/ci-examples/build-and-push-an-image/).
22
22
For a pipeline, if two builds are triggered at the same time for the same commit, one of them will pass and the other will fail.
Copy file name to clipboardExpand all lines: _docs/troubleshooting/common-issues/dockerhub-rate-limit.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Users who pull Docker images have the following limits:
37
37
>The limits depend on the[pricing plan](https://www.docker.com/pricing){:target="\_blank"} of the_user who performs the pull action_, and not the user who owns the Docker image.
38
38
39
39
40
-
If you don't have a Docker Hub integration in Codefresh, all your Docker images are pulled as an anonymous user and because Docker Hub[applies the rate limit for each IP address](https://docs.docker.com/docker-hub/download-rate-limit/), your whole Codefresh installation can easily hit the limits if you have many teams and users.
40
+
If you don't have a Docker Hub integration in Codefresh, all your Docker images are pulled as an anonymous user and because Docker Hub[applies the rate limit for each IP address](https://docs.docker.com/docker-hub/download-rate-limit/){:target="\_blank"}, your whole Codefresh installation can easily hit the limits if you have many teams and users.
Copy file name to clipboardExpand all lines: _docs/troubleshooting/common-issues/error-code-137.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,9 +36,9 @@ The error usually happens when Docker does not have enough memory, but it can al
36
36
37
37
##Solution
38
38
39
-
*[Set the build space for each pipeline build]({{site.baseurl}}/docs/pipelines/#runtime).
39
+
*[Set the build space for each pipeline build]({{site.baseurl}}/docs/pipelines/#runtime).
40
40
* If that doesn't work, you need to either simplify your application, for example, split it to microservices, or run the pipeline on a larger machine. For example if the build fails on a`SMALL` machine you should run it on a`MEDIUM` one.
41
-
You can upgrade your account to get access to more resources byvisiting your[Billing Settings](https://g.codefresh.io/account-admin/billing/).
41
+
You can upgrade your account to get access to more resources byupdating your[Billing Settings](https://g.codefresh.io/account-admin/billing/){:target="\_blank"} in Codefresh.
Copy file name to clipboardExpand all lines: _docs/troubleshooting/common-issues/failed-to-get-accounts-clusters-during-workflow.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ toc: true
12
12
13
13
When a pipeline is running, Codefresh automatically sets up several[environment variables]({{site.baseurl}}/docs/pipelines/variables/) that are available to all pipeline steps.
14
14
15
-
For Kubernetes clusters, if you have configured[at least one cluster]({{site.baseurl}}/docs/deployments/kubernetes/add-kubernetes-cluster/), the`KUBECONFIG` environment variable, containing the path to the kubeconfig file will become available in the pipeline.
15
+
For Kubernetes clusters, if you have configured[at least one cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-a-kubernetes-cluster), the`KUBECONFIG` environment variable, containing the path to the kubeconfig file will become available in the pipeline.
16
16
17
17
For more information about the`KUBECONFIG` environment variable, see the[official Kubernetes documentation](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/#set-the-kubeconfig-environment-variable){:target="_blank"}.
Copy file name to clipboardExpand all lines: _docs/troubleshooting/common-issues/forbidden-cluster-resources.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,8 @@ You can see the role access with the standard `kubectl` commands:
58
58
kubectl get clusterrole codefresh-role -o yaml
59
59
```
60
60
61
-
Make sure that the privileges are at least those described in the[integration page]({{site.baseurl}}/docs/deployments/kubernetes/add-kubernetes-cluster/#the-propersecure-way).
61
+
Make sure that the privileges are at least those described in the[integration page]({{site.baseurl}}/docs/integrations/kubernetes/#get-cluster-configuration-manually):
62
+
See_The proper secure way_ and_The proper/secure way for Kubernetes Cluster 1.24+_.
Copy file name to clipboardExpand all lines: _docs/troubleshooting/common-issues/multi-git-triggers.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ redirect_from:
8
8
toc:true
9
9
---
10
10
11
-
Codefresh has the capability to store the[pipeline definition]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#using-a-codefreshyml-for-the-source-code-repository) in the same Git repository as the source code.
11
+
Codefresh has the capability to store the[pipeline definition]({{site.baseurl}}/docs/pipelines/pipelines/#loading-codefreshyml-from-version-control) in the same Git repository as the source code.
12
12
13
13
14
14
{% include
@@ -32,13 +32,13 @@ Sometimes however, you want a pipeline to be triggered by another git repository
32
32
1. Repository A contains a deployment pipeline with associated`codefresh.yml`.
33
33
1. Repository B is creating binary artifacts that are deployed by pipeline A.
34
34
35
-
In those cases, Codefresh supports adding[multiple git triggers]({{site.baseurl}}/docs/configure-ci-cd-pipeline/triggers/git-triggers/) on the same pipeline. This way pipeline A will be triggered by commits to both repository A and repository B. Notice however that the`codefresh.yml` file used will still be fetched as mentioned in the webhook.
35
+
In those cases, Codefresh supports adding[multiple git triggers]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/) on the same pipeline. This way pipeline A will be triggered by commits to both repository A and repository B. Notice however that the`codefresh.yml` file used will still be fetched as mentioned in the webhook.
36
36
37
37
This creates issues with pipeline definitions because repository B might not have a`codefresh.yml` at all, or it might have the wrong one in the branch that actually created the webhook. Another bad scenario is when the branch mentioned in the webhook from repository B does not even exist in repository A.
38
38
39
39
To solve this issue, you can pin down the branch that will be used for the source of`codefresh.yml`. In the example above, you can specify that no matter the branch of repository B that triggered the commit, the pipeline should only use the`master` branch of pipeline A regardless of what is mentioned in the webhook.
40
40
41
-
To perform this pinning you need to use the[Codefresh CLI](https://codefresh-io.github.io/cli/installation/) and[setupauthentication](https://codefresh-io.github.io/cli/getting-started/) with your Codefresh account.
41
+
To perform this pinning you need to use the[Codefresh CLI](https://codefresh-io.github.io/cli/installation/){:target="\_blank"} and[set upauthentication](https://codefresh-io.github.io/cli/getting-started/){:target="\_blank"} with your Codefresh account.
42
42
43
43
Once this is done check that your account is locally accessible by running
44
44
@@ -111,7 +111,6 @@ In the example above we have forced the git checkout to happen out of the master
111
111
##Related articles
112
112
[Troubleshooting common issues]({{site.baseurl}}/docs/troubleshooting/common-issues)
Copy file name to clipboardExpand all lines: _docs/troubleshooting/common-issues/paging-issues-builds-images.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ or
28
28
1.`GET /workflow?page=4`
29
29
1.`GET /workflow?page=2`
30
30
31
-
The same thing was true for both[builds](https://codefresh-io.github.io/cli/builds/get-build/) and[image listing](https://codefresh-io.github.io/cli/images/get-image/).
31
+
The same thing was true for both[builds](https://codefresh-io.github.io/cli/builds/get-build/){:target="_blank"} and[image listing](https://codefresh-io.github.io/cli/images/get-image/){:target="_blank"}.
32
32
33
33
This method will**NO** longer work after January 9th 2021. The reason is that with the new implementation there is a database cursor behind the scenes that
34
34
tracks the current position within the result list. You can only go back and forward to the next or previous page but never jump to an arbitrary page.
Copy file name to clipboardExpand all lines: _docs/troubleshooting/common-issues/using-ssh-keys.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ toc: true
10
10
11
11
You can easily connect to external servers in Codefresh pipelines and run commands with them via SSH.
12
12
13
-
First, you need to create or find a Docker image with the SSH client. A good choice is[https://hub.docker.com/r/praqma/network-multitool](https://hub.docker.com/r/praqma/network-multitool) as it has several other networking tools inside.
13
+
First, you need to create or find a Docker image with the SSH client. A good choice is[https://hub.docker.com/r/praqma/network-multitool](https://hub.docker.com/r/praqma/network-multitool){:target="\_blank"} as it has several other networking tools inside.
14
14
15
15
Then create a freestyle step in your pipeline like this:
16
16
@@ -33,15 +33,16 @@ Then create a freestyle step in your pipeline like this:
33
33
{% endhighlight %}
34
34
35
35
36
-
The pipeline expects some[variables]({{site.baseurl}}/docs/pipelines/variables/) called`SSH_KEY, MY_USER, MY_HOST` that you can enter directly in the pipeline or fetch from[shared configuration]({{site.baseurl}}/docs/configure-ci-cd-pipeline/shared-configuration/).
36
+
The pipeline expects some[variables]({{site.baseurl}}/docs/pipelines/variables/) called`SSH_KEY, MY_USER, MY_HOST` that you can enter directly in the pipeline or fetch from[shared configuration]({{site.baseurl}}/docs/pipeline/configuration/shared-configuration/).
37
37
38
38
Replace`uptime`, with your own command that you want executed on the remote host.
39
39
40
-
##What to read next
40
+
##Related articles
41
+
[Troubleshooting common issues]({{site.baseurl}}/docs/troubleshooting/common-issues)
42
+
[How to use SSH keys with GIT]({{site.baseurl}}/docs/integrations/git-providers/#ssh-keys)
43
+
[How to deploy with SCP]({{site.baseurl}}/docs/example-catalog/cd-examples/deploy-to-tomcat-via-scp/)
44
+
[How to deploy with FTP]({{site.baseurl}}/docs/example-catalog/cd-examples/transferring-php-ftp/)
41
45
42
-
*[How to use SSH keys with GIT]({{site.baseurl}}/docs/integrations/git-providers/#ssh-keys)
43
-
*[How to deploy with SCP]({{site.baseurl}}/docs/yaml-examples/examples/deploy-to-tomcat-via-scp/)
44
-
*[How to deploy with FTP]({{site.baseurl}}/docs/yaml-examples/examples/transferring-php-ftp/)
Copy file name to clipboardExpand all lines: _docs/troubleshooting/personal-git-deprecation.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,10 +19,10 @@ Until July 2019, Codefresh allowed you to create a Git integration either at the
19
19
20
20
While on paper the flexibility of adding Git integrations in different levels (account or user) looks good, in practice it has been very confusing for users/customers
21
21
22
-
* Codefresh introduced login with providers which aren’t Git based - Google,[LDAP]({{site.baseurl}}/docs/enterprise/single-sign-on/sso-ldap/),[SAML]({{site.baseurl}}/docs/enterprise/single-sign-on/sso-setup-saml2/). This was causing problems for accounts which started creating pipelines leveraging the personal git context of each user and having new users signing up without a Git provider
22
+
* Codefresh introduced login with providers which aren’t Git based - Google,[LDAP]({{site.baseurl}}/docs/single-sign-on/ldap/),[SAML]({{site.baseurl}}/docs/single-sign-on/saml/). This was causing problems for accounts which started creating pipelines leveraging the personal git context of each user and having new users signing up without a Git provider
23
23
* Codefresh required Git permissions from each user that signed up instead of allowing to create a dedicated integration to your git provider of choice, allowing a company to better manage codefresh access control to their Git organization
24
24
25
-
These problems were exacerbated with the introduction of[explicit clone steps]({{site.baseurl}}/docs/troubleshooting/git-step-migration/).
25
+
<!---These problems were exacerbated with the introduction of [explicit clone steps]({{site.baseurl}}/docs/troubleshooting/git-step-migration/).-->
26
26
27
27
To this end, personal Git providers (i.e. Git integration tied to a person instead of an*account*/company) were deprecated in July 2019. This change makes Git integrations much more consistent, especially for people that work within a company organization.
28
28
@@ -33,13 +33,13 @@ To this end, personal Git providers (i.e. Git integration tied to a person inste
33
33
34
34
Make sure that you have at least one Git integration defined in your account (if until now you only used the implicit one that was created when you signed-up with Codefresh)
35
35
36
-
Then, for all existing[pipelines]({{site.baseurl}}/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines/):
36
+
Then, for all existing[pipelines]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/):
37
37
38
-
*make sure that they have an[explicit git clone step]({{site.baseurl}}/docs/pipelines/steps/git-clone/)
39
-
*the git clone step has an explicit`git` property that defines the provider (do not leave empty this property )
40
-
*the`git` provider has an actual value and**not**`CF-default`. This value used to represent the personal git provider of a user and is now deprecated. Use the name of an actual git integration as is defined in the[providers page]({{site.baseurl}}/docs/integrations/git-providers/)
38
+
*Make sure that they have an[explicit git clone step]({{site.baseurl}}/docs/pipelines/steps/git-clone/)
39
+
*The git clone step has an explicit`git` property that defines the provider (do not leave empty this property )
40
+
*The`git` provider has an actual value and**not**`CF-default`. This value used to represent the personal git provider of a user and is now deprecated. Use the name of an actual git integration as is defined in the[providers page]({{site.baseurl}}/docs/integrations/git-providers/)
41
41
42
-
Once that is done, contact Codefresh via[http://support.codefresh.io](http://support.codefresh.io) or email, and we can take care of automatic migration of all your existing[triggers]({{site.baseurl}}/docs/configure-ci-cd-pipeline/triggers/git-triggers/) that exist in pipelines that are still using a personal Git provider.
42
+
Once that is done, contact Codefresh via[http://support.codefresh.io](http://support.codefresh.io){:target="\_blank"} or email, and we can take care of automatic migration of all your existing[triggers]({{site.baseurl}}/docs/pipelines/triggers/git-triggers/) that exist in pipelines that are still using a personal Git provider.