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/pipeline-settings.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,18 +42,18 @@ max-width="80%"
42
42
43
43
Here you can define global template behavior. The options are:
44
44
45
-
* Enable[pipeline templates]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/pipelines/#using-pipeline-templates) for users. If this is enabled some pipelines can be marked as templates and users can still select them when creating a new pipeline.
46
-
* Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when[creating a new pipeline]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/pipelines/#creating-new-pipelines).
45
+
* Enable[pipeline templates]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#using-pipeline-templates) for users. If this is enabled some pipelines can be marked as templates and users can still select them when creating a new pipeline.
46
+
* Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when[creating a new pipeline]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#creating-new-pipelines).
47
47
48
48
Note that templates are simply normal pipelines “marked” as a template. There is no technical difference between templates and actual pipelines.
49
49
50
50
##Pipeline YAML Section
51
51
52
52
Here you can restrict the sources of pipeline YAML that users can select. The options are:
53
53
54
-
* Enable/Disable the[inline editor]({{site.baseurl}}/docs/docs/configure-ci-cd-pipeline/pipelines/#using-the-inline-pipeline-editor) where YAML is stored in Codefresh SaaS
54
+
* Enable/Disable the[inline editor]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#using-the-inline-pipeline-editor) where YAML is stored in Codefresh SaaS
55
55
* Enable/disable pipeline YAML from connected Git repositories
You need to allow at least one of these options so that users can create new pipelines. We suggest leaving the first option enabled when users are still learning about Codefresh and want to experiment.
59
59
@@ -78,10 +78,10 @@ Here you can decide if the build step will push images or not according to your
78
78
2. All built images are automatically pushed to the default registry
79
79
3. All built images are NOT pushed anywhere by default
80
80
81
-
Note that this behavior is simply a convenience feature for legacy pipelines. Users can still use a[push step]({{site.baseurl}}/docs/docs/codefresh-yaml/steps/push/) in a pipeline and always push an image to a registry regardless of what was chosen in the build step.
81
+
Note that this behavior is simply a convenience feature for legacy pipelines. Users can still use a[push step]({{site.baseurl}}/docs/codefresh-yaml/steps/push/) in a pipeline and always push an image to a registry regardless of what was chosen in the build step.