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/administration/account-user-management/access-control.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
@@ -114,7 +114,7 @@ You can assign multiple tags to each cluster, making it easy to define multiple
114
114
115
115
>By default, all clusters, with and without tags, are displayed and can be edited by all users (but not deleted). As soon as you add at least one tag to a cluster, the cluster is only accessible to users with the required policy rules (explained in the next sections).
116
116
117
-
###ConfigureCIpipelines with policy attributes<!---TITLE: add tags to pipelines-->
117
+
###Configure pipelines with policy attributes<!---TITLE: add tags to pipelines-->
118
118
119
119
Similar to Kubernetes clusters, you can also add tags to specific pipelines.
Copy file name to clipboardExpand all lines: _docs/deployments/helm/custom-helm-uploads.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 @@ Helm packages are just TAR files. Helm repositories are simple file hierarchies
12
12
You can run custom commands and manually upload indexes and packages to a Helm repo.
13
13
14
14
>This articles shows some non-standard Helm examples.
15
-
For the basic use cases, or if you are just getting started with Helm, see our[Helm quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/) and[Using Helm inCIpipelines]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/).
15
+
For the basic use cases, or if you are just getting started with Helm, see our[Helm quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/) and[Using Helm in pipelines]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/).
16
16
17
17
##Package a Helm chart
18
18
Below is an example of a freestyle step in a Codefresh pipeline that packages the Helm chart and then extracts the chart name from the command output. It also saves that package name in an environment variable for later use.
Copy file name to clipboardExpand all lines: _docs/installation/installation-options.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
@@ -9,7 +9,7 @@ To be changed and updated for ProjectOne
9
9
The Codefresh platform supports two different installation environments, each with different installation options.
10
10
11
11
* CI/CD installation environment
12
-
The CI/CD installation environment is optimized for Continuous Integration/Delivery with Codefresh pipelines.CI pipelines created in Codefresh fetch code from your Git repository, packages/compiles the code, and deploys the final artifact to a target environment.
12
+
The CI/CD installation environment is optimized for Continuous Integration/Delivery with Codefresh pipelines.Pipelines created in Codefresh fetch code from your Git repository, packages/compiles the code, and deploys the final artifact to a target environment.
13
13
14
14
The CI/CD installation environment supports these installation options:
15
15
* Hybrid, where the Codefresh CI/CD UI runs in the Codefresh cloud, and the builds run on customer premises