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

Commitb6fa133

Browse files
merge main
2 parents9540861 +fd44035 commitb6fa133

File tree

5 files changed

+17
-15
lines changed

5 files changed

+17
-15
lines changed

‎_docs/administration/codefresh-runner.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,8 @@ Install the Codefresh Runner on your Kubernetes cluster to run pipelines and acc
1313

1414
[Skip to quick installation→](#installation-with-the-quick-start-wizard)
1515

16-
>***Note:** a runner installation is needed for each cluster_running_ Codefresh pipelines. A runner is**not** needed
17-
in clusters used for_deployment_. It is possible to deploy applications on clusters other than the ones the runner is deployed on.*
16+
>**Note:** a runner installation is needed for each cluster_running_ Codefresh pipelines. A runner is**not** needed
17+
in clusters used for_deployment_. It is possible to deploy applications on clusters other than the ones the runner is deployed on.
1818

1919
The installation process takes care of all runner components and other required resources (config-maps, secrets, volumes).
2020

‎_docs/codefresh-yaml/steps.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -247,7 +247,7 @@ version: '1.0'
247247
kind: step-type
248248
metadata:
249249
name: <codefresh_account_name>/<step_name>
250-
isPublic:true
250+
isPublic:false
251251
description: >-
252252
The plugin exports KV pairs from Hashicorp Vault to Codefresh pipeline ENV
253253
variables
@@ -442,7 +442,7 @@ version: '1.0'
442442
kind: step-type
443443
metadata:
444444
name: kostis-codefresh/node-version
445-
isPublic:true
445+
isPublic:false
446446
description: >-
447447
The plugin exports as an environment variable the application version from package.json
448448
sources:
@@ -600,7 +600,7 @@ version: '1.0'
600600
kind: step-type
601601
metadata:
602602
name: kostis-codefresh/output-parameters-example
603-
isPublic:true
603+
isPublic:false
604604
description: >-
605605
The plugin shows how you can export output parameters
606606
sources:
@@ -795,7 +795,7 @@ version: '1.0'
795795
kind: step-type
796796
metadata:
797797
name: kostis-codefresh/mvn-version
798-
isPublic:true
798+
isPublic:false
799799
description: >-
800800
The plugin exports as an environment variable the mvn coordinates from pom.xml
801801
sources:
@@ -1005,7 +1005,7 @@ version: '1.0'
10051005
kind: step-type
10061006
metadata:
10071007
name: kostis-codefresh/multi-git-clone
1008-
isPublic:true
1008+
isPublic:false
10091009
description: >-
10101010
This pipeline plugin shows templating of custom steps
10111011
sources:

‎_docs/codefresh-yaml/steps/approval.md‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -147,6 +147,9 @@ max-width="90%"
147147

148148
>Notice that if you do decide to keep the volume after an approval, the pipeline will still count as "running" against your pricing plan (if you use the SAAS version of Codefresh). 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.
149149
150+
>Notice also that you if you use the[Hybrid version]({{site.baseurl}}/docs/administration/behind-the-firewall/) of Codefresh and your[Runner]({{site.baseurl}}/docs/administration/codefresh-runner/) is setup with local volumes, then the volume will only be present if the dind pod
151+
is scheduled in the same node once the pipeline resumes. Otherwise the volume will not be reused.
152+
150153
##Controlling the rejection behavior
151154

152155
By default if you reject a pipeline, it will stop right away and it will be marked as failed. All subsequent steps after the approval one will not run at all.

‎_docs/configure-ci-cd-pipeline/secrets-store.md‎

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,6 @@ steps:
6767

6868
You can also use secrets in the GUI screens that support them. Currently you can use secrets in:
6969

70-
* Git integration for[behind-the-firewall Git installations]({{site.baseurl}}/docs/integrations/git-providers/#github)
7170
* Values in[shared configuration]({{site.baseurl}}/docs/configure-ci-cd-pipeline/shared-configuration/)
7271
* Integration with[cloud storage]({{site.baseurl}}/docs/testing/test-reports/#connecting-your-storage-account)
7372

@@ -77,11 +76,11 @@ Where secret integration is supported, click on the lock icon and enable the tog
7776
{% include
7877
image.html
7978
lightbox="true"
80-
file="/images/pipeline/secrets/lock-icon.png"
81-
url="/images/pipeline/secrets/lock-icon.png"
82-
alt="Usinga connected secretinthe Codefresh GUI"
83-
caption="Usinga connected secretinthe Codefresh GUI"
84-
max-width="100%"
79+
file="/images/pipeline/shared-configuration/shared-conf-secret-integration.png"
80+
url="/images/pipeline/shared-configuration/shared-conf-secret-integration.png"
81+
alt="Usingexternal secretsinshared configuration values"
82+
caption="Usingexternal secretsinshared configuration values"
83+
max-width="50%"
8584
%}
8685

8786
If you have already specified the resource field during secret definition the just enter on the text field the name of the secret directly, i.e.`my-secret-key`.

‎_docs/new-helm/helm-environment-promotion.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -174,8 +174,8 @@ max-width="40%"
174174
By default Codefresh will use a built-in install/upgrade pipeline for performing the promotion. You can choose your own pipeline from the promotion dialog. That pipeline will be automatically provided with the following[environment variables]({{site.baseurl}}/docs/new-helm/helm-releases-management/#overriding-the-default-helm-actions):
175175

176176
*`CF_HELM_RELEASE` - name of release
177-
*`CF_HELM_KUBE_CONTEXT` - kubectl context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deploy-to-kubernetes/manage-kubernetes/#work-with-your-services))
178-
*`CF_HELM_NAMESPACE` -namespace where release is stored now
177+
*`CF_HELM_KUBE_CONTEXT` -`kubectl` context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deploy-to-kubernetes/manage-kubernetes/#work-with-your-services))
178+
*`CF_HELM_NAMESPACE` -Tiller Namespace if you use Helm 2
179179
*`CF_HELM_INSTALLATION_NAMESPACE` - namespace where release is promoted to
180180
*`CF_HELM_CONTEXTS` -[shared configuration]({{site.baseurl}}/docs/configure-ci-cd-pipeline/shared-configuration) Helm contexts
181181
*`CF_HELM_VALUES` - Helm chart values

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp