Define global options for pipeline templates, yaml sources and approval behavior
To access your global pipeline settings navigate to https://g.codefresh.io/account-admin/account-conf/pipeline-settings or click on Account settings on the left sidebar and then choose Pipeline settings item on the next screen.
On this page, you can define global parameters for the whole Codefresh account regarding pipeline options. Users can still override some of these options for individual pipelines.
Here you can define global template behavior. The options are:
- Enable 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.
- Decide if users can clone an existing pipeline (along with its triggers and associated parameters) when creating a new pipeline.
Note that templates are simply normal pipelines “marked” as a template. There is no technical difference between templates and actual pipelines.
Pipeline YAML Section
Here you can restrict the sources of pipeline YAML that users can select. The options are:
- Enable/Disable the inline editor where YAML is stored in Codefresh SaaS
- Enable/disable pipeline YAML from connected Git repositories
- Enable/disable pipeline YAML from external URLs
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.
Advanced Pipeline Options
Here you can set the defaults for advanced pipeline behavior. The options are:
- Keep or discard the volume when a pipeline is entering approval state
- Whether pipelines in approval state count or not against concurrency
Note that the first option affects pipeline resources and/or billing in the case of SaaS pricing. It will also affect users of existing pipelines that depend on this behavior. It is best to enable/disable this option only once at the beginning.
Default Behavior for Build Step
Here you can decide if the build step will push images or not according to your organization’s needs. The options are:
- Users need to decide if an image will be pushed or not after it is built
- All built images are automatically pushed to the default registry
- All built images are NOT pushed anywhere by default
Note that this behavior is simply a convenience feature for legacy pipelines. Users can still use a push step in a pipeline and always push an image to a registry regardless of what was chosen in the build step.