diff --git a/_docs/installation/runner/install-codefresh-runner.md b/_docs/installation/runner/install-codefresh-runner.md index a46d44bba..4acd4fe12 100644 --- a/_docs/installation/runner/install-codefresh-runner.md +++ b/_docs/installation/runner/install-codefresh-runner.md @@ -399,7 +399,7 @@ If your builds are stuck in Pending or failing with `Failed to validate connecti ### For Codefresh Runner installed with legacy CLI 1. Delete `codefresh-certs-server` k8s secret; -2. Download [`./configure-dind-certs.sh` script](https://github.com/codefresh-support/cf-utils/blob/master/configure-dind-certs.sh) and run it: +2. Download [`./configure-dind-certs.sh` script](https://github.com/codefresh-io/cf-utils/blob/master/configure-dind-certs.sh) and run it: ```shell # Ensure the following environment variables are defined before running the command: diff --git a/_docs/kb/articles/speed-builds-intermediate-images.md b/_docs/kb/articles/speed-builds-intermediate-images.md deleted file mode 100644 index b667842f1..000000000 --- a/_docs/kb/articles/speed-builds-intermediate-images.md +++ /dev/null @@ -1,46 +0,0 @@ ---- -title: "How To: Speed up Builds by Using Intermediate Images to Cache Dependencies" -description: -group: kb -sub-group: articles -toc: true -kb: false -ht: true -common: false -categories: [Pipelines] -support-reviewed: 2023-05-04 LG ---- - -## Overview - -If you have a build pipeline where the dependencies of your build do not often change, you can speed up those builds by building those dependencies into an intermediate container image. - -## Details - -### Example Project - - - -Inside of this project there is a example pipeline for Codefresh Classic that demonstrates how to selectively rebuild the intermediate container if the dependency's change: - - - -### Technical details - -This example checks to see if the `/dependency/dependencies.list` file has changed in the `dependency_evaluation` step, by running running the below command: - -```shel -git diff --name-only HEAD~1 HEAD | grep dependency/dependencies.list -``` - -This checks all the file changes made in the last commit, and then filters this list of changes to see if the `dependencies.list` file is in that list of changes. The result of that test is then checked to see if a build step is required to run. - -After doing so, the pipeline continues with the next step triggering on either a successful build, or a "failed" ('not required') result of the dependency_evaluation step. - -### Key Takeaway - -You don't have to rebuild your entire project on every commit. By using Conditional Execution [1] of steps and detecting when your dependencies change, you can further speed up your pipeline. - -## Related Items - -[1] diff --git a/_docs/kb/articles/stuck-in-validating-docker-daemon.md b/_docs/kb/articles/stuck-in-validating-docker-daemon.md index cdd856296..52b920ab4 100644 --- a/_docs/kb/articles/stuck-in-validating-docker-daemon.md +++ b/_docs/kb/articles/stuck-in-validating-docker-daemon.md @@ -20,4 +20,4 @@ Build not starting, showing only `Validating connection to Docker daemon` in `In 1. Stop the build and restart it. 2. [Check for outages here.](https://status.codefresh.io) 3. If using an on-premise Codefresh instance or a Codefresh hybrid runner on your cluster, please check their status. -4. Please contact our support team with a link to the build showing the issue, as well as any details you may have. For Codefresh runner issues, please include [a set of runner cluster logs](https://github.com/codefresh-support/hybrid-runner-support). +4. Please contact our support team with a link to the build showing the issue, as well as any details you may have. For Codefresh runner issues, please include [a set of runner cluster logs](https://github.com/codefresh-io/codefresh-support-package). diff --git a/_docs/kb/support-ticket-examples.md b/_docs/kb/support-ticket-examples.md index 8091cd43d..c58b49c5c 100644 --- a/_docs/kb/support-ticket-examples.md +++ b/_docs/kb/support-ticket-examples.md @@ -58,7 +58,7 @@ To troubleshoot issues or bugs effectively, Codefresh Support requires a detaile 1. **Engine and DIND logs** for the failed build: - While the build is running, navigate to the cluster, and locate the pods named `engine-[buildID]` and `dind-[buildID]`. - Save those logs to a file and attach them to the ticket. - - Alternatively, you can use the [Codefresh Support Package](https://github.com/codefresh-support/codefresh-support-package){:target="\_blank"} to collect the required data *while the affected build is running and the error message is received*. + - Alternatively, you can use the [Codefresh Support Package](https://github.com/codefresh-io/codefresh-support-package){:target="\_blank"} to collect the required data *while the affected build is running and the error message is received*. 1. **Helm values file** (to identify overrides such as images or other configurations). #### UI: Slowness and other issues @@ -84,7 +84,7 @@ To troubleshoot issues or bugs effectively, Codefresh Support requires a detaile 1. **Ebs-csi pod logs** in the `kube-system` namespace if there are volume issues and you're using `ebs-csi`. 1. Overview of cluster **scale up/down events** for the relevant timeframe. -> Alternatively, to collect the data for 3 through 6, use the [Codefresh Support Package](https://github.com/codefresh-support/codefresh-support-package){:target="\_blank"}. +> Alternatively, to collect the data for 3 through 6, use the [Codefresh Support Package](https://github.com/codefresh-io/codefresh-support-package){:target="\_blank"}. #### Security concerns